I understand the concept that multiple trades from multiple EAs can collide if they try and trade simultaneously; I have implemented the global semaphore logic to protect against this or OrderSend/Close/Modify/Close/Delete.
However, I have other areas of my EA where I check order status, select orders, request various order contents having selected the order via OrderSelect.
What is not clear is - does the '146' issue affect all calls to the trade context - such as OrderSelect - or is it limited to calls like OrderSend/Close/Delete/Modify? The documentation does not seem to provide information on which of the possible 'Order..." calls are subject to the single threading issue.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
I understand the concept that multiple trades from multiple EAs can collide if they try and trade simultaneously; I have implemented the global semaphore logic to protect against this or OrderSend/Close/Modify/Close/Delete.
However, I have other areas of my EA where I check order status, select orders, request various order contents having selected the order via OrderSelect.
What is not clear is - does the '146' issue affect all calls to the trade context - such as OrderSelect - or is it limited to calls like OrderSend/Close/Delete/Modify? The documentation does not seem to provide information on which of the possible 'Order..." calls are subject to the single threading issue.
Regards Michael