You could go on and on, but I'm not sure you need to. There is no effect on performance, only on productivity. To be more precise, it affects speed. Although multicurrencies are already slow, and adding speed reduction to them is not good
You could go on and on, but I'm not sure you need to. There is no effect on performance, only on productivity. To be more precise, it affects speed. Although multicurrencies are already slow, and adding speed reduction to them is not good
I have already noticed that not all orders may close at the first time and then on the next tick the unclosed positions don't fall under the Equity over balance condition... I have changed the trawl a little
I should make a Magik for my pairs - and process them.... a small cycle before the closing cycle... - counting closing attempts (global closing cycle) - giving a beep :)
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.
After we lose?
I did not say that.
For example, there will be errors when closing positions. They may not all close together.
I didn't say that.
For example, there will be errors when closing positions. They may not all close together.
Increased the slippage to 5. And there's while(true) after error - continue until ironclad execution of command? Can't figure it out yet.
Increased the slippage to 5. And there is while(true) after error - continue until ironclad execution of command? Can't figure it out yet.
To close, a reverse loop is done
YYYYYYY! Why did you yank error handling, Slava? I did.
I'll fix it now, post it - don't take it away again.
I'll make sure the team comes to a clear conclusion
A reverse cycle is done to close
Uh-oh! Thank you!
Exactly, there are fewer orders
You could go on and on, but I'm not sure you need to. There is no effect on performance, only on productivity. To be more precise, it affects speed. Although multicurrencies are already slow, and adding speed reduction to them is not good
You could go on and on, but I'm not sure you need to. There is no effect on performance, only on productivity. To be more precise, it affects speed. Although multicurrencies are already slow, and adding speed reduction to them is not good
Yes, we should continue, if time allows.
Yes, we should continue, if time permits.
It won't be continued until tomorrow.
Uh-oh! Oh, thank you!
That's right, the orders are getting smaller.
I should make a Magik for my pairs - and process them.... a small cycle before the closing cycle... - counting closing attempts (global closing cycle) - giving a beep :)