You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi just want ask and clarify somethings in terms of opening a file. Since both the master and slave are opening the same file which is the Tradecopy.csv, there would be a chance that both EA could open the file at the same time which could cause some errors since writing and reading into a file can't be done on the same time. And from what I've seen on the code it'll just print out the error and it'll go back to the start continuing the loop. Is there a better way to check on a file if there are records or modifications which happens on that file without using for loop again and again?
The text was updated successfully, but these errors were encountered:
You've raised a valid concern regarding concurrent access to the TradeCopy.csv file. A potential solution could involve utilizing an intermediary that supports simultaneous access. I've considered options like sqlite3 or even a more sophisticated approach using ZMQ combined with a database. However, integrating external DLLs or setting up a server would significantly increase the complexity of the system. Such enhancements might be more justified if there's a future requirement, such as receiving signals from Telegram channels or similar sources.
Hi just want ask and clarify somethings in terms of opening a file. Since both the master and slave are opening the same file which is the Tradecopy.csv, there would be a chance that both EA could open the file at the same time which could cause some errors since writing and reading into a file can't be done on the same time. And from what I've seen on the code it'll just print out the error and it'll go back to the start continuing the loop. Is there a better way to check on a file if there are records or modifications which happens on that file without using for loop again and again?
The text was updated successfully, but these errors were encountered: