RickD: I wonder - what's the reason for doing it that way ... I understand that if we are using asynchronous OrderSendAsync, both OnTrade and OnTradeTransaction can be handled. With OrderSend we want to have simple behavior, like in MT4. Once it is called, we obtain in the output already modified open positions and history. There is a subtle point. If the current state is stored in a global variable and the expectation of state changes lasts long enough, and the trader changes the EA parameters, the global variables will be reset and the state will be discarded.
This is the vulnerability that can be gained from the necessity of the mentioned remembering.
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.
This is not really a simplification. In the original version MACRO+2*f+g1+g2=5 - you have: MACRO+2*f+2*g1+2*g2=7.
I wonder - what's the reason for doing it that way ...
I understand that if we are using asynchronous OrderSendAsync, both OnTrade and OnTradeTransaction can be handled. With OrderSend we want to have simple behavior, like in MT4. Once it is called, we obtain in the output already modified open positions and history.
There is a subtle point. If the current state is stored in a global variable and the expectation of state changes lasts long enough, and the trader changes the EA parameters, the global variables will be reset and the state will be discarded.
What does GetLastError() return ?
ERR_INDICATOR_DATA_NOT_FOUND
4806
Requested data not found
"Handle" of the indicator is received, but the data is "not found" when trying to copy.
I have a project of dozens of mqh. All of them are in different folders. And some mqh have the same name, but different path (builds, in short).
But when compiling, the log shows the names of mqh files WITHOUT paths! Add, please.
What's wrong with the previous badges? They were more fun, weren't they?
What's wrong with the previous badges? They were more fun, weren't they?
#undef and #ifdef MACRO would apply to all overloads at once.