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's not quite clear what's wrong here.
TimeCurrent in and out of any On functions returns the same values. There are no nuances.
TimeCurrent in and out of any On functions returns the same values. There are no nuances.
Here is the answer to the question.
Forum on trading, automated trading systems and trading strategies testing
Peculiarities of mql5 language, tips and tricks
Slava, 2018.01.25 07:41
Are you going to measure exactly one second with Sleep(1000) slip?
And you do not know that timer in processor has 15 ms error?
Here's the answer to the question.
Why the 2 second delay then?
Tried with your code, still lags behind.
Have you tried it simply on a millisecond (1) timer?
Why the two-second delay then?
Why not?
It's not like the error is alternating one way and the other.
Why not?
It doesn't mean that the errors alternate one way and the other.
Was it a coincidence that the 1st timer call was at 985+ milliseconds and then the timer was delayed 2 times by 16ms? Very unlikely.
Was it a coincidence that the 1st timer call was at 985+ milliseconds and then 2 times the timer was delayed by 16ms? Very unlikely.
I have neither the desire nor the knowledge to prove it. I just admit from my point of view that it is possible.
I have no desire or knowledge to prove it. I just from my point of view allow the possibility of such a variant.
Not taken as an assumption.
Forum on trading, automated trading systems and strategy testing
Market closed
Alexey Viktorov, 2018.01.25 08:07
Here is the answer to the question.
Not taken as an assumption.
If the timer in the processor has a margin of error, then in my opinion it is possible to assume that
Forum on trading, automated trading systems and strategy testing
Market closed
Andrey Khatimlianskii, 2018.01.25 13:20
It coincided that the 1st timer call was at 985+ milliseconds and then 2 times the timer was delayed by 16ms? Very unlikely.
Unless not necessarily by 16, but in the same direction.