![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
Urain:
Так что это или баг терминала, или серверной истории. Но скорее терминала, тк отчёты на чемпе скорее с серверной истории восстанавливались.
That's funny. I wasn't paying attention. Clearly explained.
Found it, it defaults to sorting by time and needs to sort by transaction number. Then everything is correct.
So there are no errors? The whole point is to count/sort the trades by ticket number, not by time.
I was only superficially reviewing the reports, not calculating position states.
So there are no bugs? The whole point is to count/sort transactions by ticket and not by time.
I was only superficially reviewing the reports, not calculating position states.
Exactly, it's just that when you save a report there is no automation of this process and it needs to be carefully monitored. I don't think every user will pay attention to this and as a result there will be bugs when parsing the report.
ZS I added sorting after parsing the report. As a result, it all worked for me, but I predict that more than one programmer will have a hard time with this feature.
During optimization, name of optimization parameter is displayed in the upper right corner of the optimization graph.
When observing the optimisation, this inscription is annoying because the new maximum is always hidden behind this inscription.
Renat, let's move it to the LEFT top corner! Or the bottom right. Or lower left... Anywhere, just take it out of the upper right corner, for God's sake. Please! :)
// Or at least make it pale and put it in the background so it doesn't obscure the information.
During optimization, name of optimization parameter is displayed in the upper right corner of the optimization graph.
When observing the optimisation, this inscription is annoying because the new maximum is always hidden behind this inscription.
Renat, let's move it to the LEFT top corner! Or to the bottom right. Or lower left... Anywhere, just take it out of the upper right corner, for God's sake. Please! :)
// Or at least make it pale and put it in the background so it doesn't obscure the information.
Please tell me where I went wrong. I am trying to write a simple script that deletes position and pending orders on the current instrument. Here:
The script hangs when there is a position. When debugging it, I found out that it freezes when checking for position. When loop condition while(check_position()==true) starts to be checked, control is passed to check_position() and the first time the function is executed normally, it returns true. But then the loop's body is not executed; it starts checking the condition again and control gets to check_position() and after return(order_exsist) operator does not return to the loop's condition; it goes to the beginning of check_position() function. Please tell me where I made a mistake.Please tell me where I went wrong. I am trying to write a simple script that deletes position and pending orders on the current instrument. Here it is:
The script hangs when there is a position. When debugging it, I found out that it freezes when checking for the position. When loop condition while(check_position()==true) starts checking, control is passed to check_position() function and at first time function is executed normally, returns true. But then the loop's body is not executed; it starts checking the condition again and control gets to check_position() and after return(order_exsist) operator does not return to the loop's condition; it goes to the beginning of check_position() function. Please tell me where I must be mistaken.If there is a position, you will get an infinite loop because
Equals
There is no way to break out of the loop in the code because there is no break in the operator's body;