The great and terrible MT4 forever (or how to strategise a transition) - page 23
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
it seems to work like this:
but it's very slow and it's not a very good solution.
it seems to work like this:
but it's very slow, and it's not a very good solution.
You have made almost that option.
Forum on trading, automated trading systems and trading strategy testing
The Great and Horrible MT4 Forever (or how to strategize migration)
fxsaber, 2021.05.09 00:36
You can use this condition:
In general, we need some kind of synchronous RefreshPositions() from the developers which will reliably return from the server the state of positions + orders
Then the one who needs it sends orders asynchronously, and the one who doesn't needs it waits for the server's answer in the body of the program.
That's the thing, it did. When the script finishes running, one or two positions are left hanging (depending on how many prints are inserted into the code).
Code:
Result:
To complete the picture, add the trade event listener from the article https://www.mql5.com/ru/articles/2513 to the adjacent chart
To see the order of events
+ addrequest_id - Request ID to be set by the terminal when the order is sent
How many orders are really sent there
imho, OnTradeTransaction() also does not guarantee anything, the sequence of events is not guaranteed, as well as the information delivery to the terminal itself - I mean the case with not the most reliable internet providers
there is no mechanism to control OnTradeTransaction(), or I have or have not received all events in strict sequence
PZY: I wish some not too busy MQ programmer could find 2 hours to write a function returning a text description of the error code. That would be great, and there would be less writing in MQL5 and no need in MT4 - let them do it manually
;)
Found in codobase and the latest codes added
So people asked for access to the black box - they got it.
Now you have to do the synchronisation yourself. Asked? They did. Did they? They did. Is it good? They said it would be good. Once it was given, it became bad.
1. I didn't ask for it.
2. no one said the price would be data integrity, which is much more important.
instead of naked demagoguery like "our fault", can you offer a solution without crutches?
Found in kodobase and added the latest codes
I did the same code in half an hour from ME help - opened the error codes, highlighted the mouse, Ctrl+C , created an empty Excel page, Ctrl+V and added columns with case: and inverted commas
then Ctrl+C+Ctrl+V in ME
okay, apparently "endure hardship" is not just an article from the military manual, it's more like our mentality
1. I didn't ask for it.
2. no one said that the price would be data integrity, which is much more important.
Instead of "blame yourself" demagoguery, can you suggest a solution without crutches?
I did the same code in half an hour from ME help - opened error codes, highlighted the mouse, Ctrl+C , created an empty Excel page, Ctrl+V and added columns with case: and inverted commas
then Ctrl+C+Ctrl+V in ME
okay, apparently "endure hardship" is not just an article from the military manual, it's more like our mentality