Errors, bugs, questions - page 3147

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
Good day to all. Could you please advise whether Sleep() is executed in the Expert Advisor testing mode (testing on real ticks, of course)?
In progress - the Tester time is changed by an appropriate amount.
Executed - the Tester time is changed by an appropriate amount.
Thank you very much!
Is it possible to find the size of the very tick in mql5, after which a position was opened?
It turns out that you can. The for loop is inserted in a separate function, in the OnTick() function or at your own discretion. I am interested in the opinion of others. For example, I need it to create an ultra-precise system. Therefore, I'm writing without libraries, including functions for opening and closing positions. Whoever says what, mqh libraries slow down the work, for example compilation takes 1.5 times longer. It's better to write everything in one file. The style, OOP or procedural, does not matter. MQL5 will never become a language on the level of C++, it is limited. The point is in libraries.
I'm sick of this bug - there is an indicator, there is an expert working on it. I change the indicator and recompile it. The indicator changes can be clearly seen on the chart - the Expert Advisor is run in the tester - but it is as if it didn't change anything. The same result.
If I restart the terminal and pass the tester after that it will generate a new code.
What is this hack, I do not understand.
I removed indicator ex5. Tester continues to run as if nothing has happened. Where does it get the file to run????
3184
Strange behaviour in the indicator.
The for loop goes into the body, not on every tick, but only once on a new candle.
But i == 0 and the given condition allows i>=0
on the tick on the same bar limit = 0
so the first value of i = -1 and condition i>=0
that is why it does not go into the loop.
at the tick on the same bar limit = 0
so the first value i = -1 and the condition i>=0
that's why it doesn't go into the loop.
Thanks, I missed the one.
But now indicator buffer IndBuff[i] is doing its head in, array out of range.
What does it need? Why doesn't it allocate to initial i=limit ?
Thanks, missed the one.
But now indicator buffer IndBuff[i] is doing the brains, array out of range.
What does it need? Why it does not allocate to initial i=limit ?
So on every bar it goes into a loop, while it needs to go into a loop on every tick.
It used to work like this
for the ticks i>=0,
for bars i>0
Now I do not know how to work with the buffer.
That's because IndBuff is not allocated to rates_total + 1
And ArrayResize is not applicable to it.
They broke the for construct. Now we have to use if-arses to do everything?