From theory to practice - page 226
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
how to dock the highlighted?
I have already written. My work is not done by OnTick, but by OnTimer = 300 ms.
I don't know if it is an error or not in MQL, but it happens very rarely that several trades are opened, despite the strict condition of OrdersTotal()=0.
It is a very unpleasant thing. That is why I very strictly adhere to MoneyManagement, and do not rush to move to larger lots.
I have already written. I'm not working by OnTick, but by OnTimer = 300 ms.
I don't know if it is an error or not in MQL, but it happens very rarely that several trades are opened, despite the strict condition of OrdersTotal()=0.
It is a very unpleasant thing. That's why I'm very strict about MoneyManagement, and not in a hurry to move to larger lots.
come on....
Rename OnTick() to Trading()
then at the very end of OnTick() add: Trading();
come on....
On different pairs, of course. That's how it is sometimes. But, very rarely. But, very unpleasant.
Hello pure physicists!
I'll tell you one clever thing, but don't be offended :-))
It's been too little time to draw conclusions about the performance of the system. We need to see how it works under different market conditions. To make a long story short...
This is an anti-scientific approach - to check ts for quality, and even with your own money. According to all canons of modern paradigm of verbiage in science, now it is more correct to start PR and selling the TS at once. As a result, the process of checking its profitability is reduced many times, blue circles appeared under the eyes - it means it is losing.
:)))))))))))))) pattalom....
I don't know if this is a bug or not in MQL, but it happens very rarely that several trades open, despite the strict condition on OrdersTotal()=0.
This is a very unpleasant thing.
It's not so much an error as an undocumented terminal operation - it's related to parallel processing of threads and therefore data doesn't have time to update and causes calculation errors and false trade actions...
It's not so much an error as an undocumented terminal operation - it's related to parallel processing of threads and therefore data doesn't have time to update and calculation errors and false trade actions occur...
Ticks arrive in less than 300ms
Who writes programs like that?
Documentation can't point to a bug in the robot...
Ticks arrive in less than 300ms
Who writes software like that?
The documentation cannot indicate a flaw in the robot...
This is a normal situation of 3 ticks per second and the program must be able to handle it correctly... If you read the documentation on ticks processing, then in practice it will not turn out exactly as it is described there - hence the generation of deals even when they are forbidden programmatically...
It is not desirable to use OnTimer() for signal 'mining' and trading functions.
Or you can synchronize the robot in terms of "What came first - the chicken or the egg?
I have already written. I'm not working by OnTick, but by OnTimer = 300 ms.
I don't know if it is an error or not in MQL, but it happens very rarely that several trades are opened, despite the strict condition of OrdersTotal()=0.
It is a very unpleasant thing. That's why I very strictly adhere to MoneyManagement and take my time moving to larger lots.
You should check the result of transaction execution first, and then verify it with OrdersTotal.
If order has been sent, it does not mean it has already been executed (may be currently being processed) and order total will return 0.