When compiling, if OrderOpen(), OrderClose(), etc. functions are not checked, it gives a warning about this. Is there any point in writing this check if errors are logged anyway?
When compiling, if OrderOpen(), OrderClose(), etc. functions are not checked, it gives a warning about this. Is there any sense in writing this check if errors are already printed in the log?
A good "tone" of programming is a program without errors and warnings, everything else is amateurish.
When compiling, if OrderOpen(), OrderClose(), etc. functions are not checked, it gives a warning about this. Is there any point in writing this check if errors are logged anyway?
You're not going to withdraw the money earned by the Expert Advisor from the journal. Accordingly, the program must handle the errors in order to act accordingly.
Check your settings, maybe you have too many bars to display, hence the lags.
OK. Can you tell me how to reduce the number of bars you don't want?
OK. Can you tell me how to reduce the number of bars you don't want?
Service - settings - max bars in window (value should not be less than 5000). Restart the terminal and that's it.
Service - settings - max bars in window (value should not be less than 5000). Restart the terminal and that's it.
Thank you! Learned something new) Helps!
Hello, could you please tell me how to convert angle of inclination from radiant units to degrees in MQL4?
You studied geometry and stereometry in school. Not much of a problem then.
You studied geometry and stereometry in school. Not much of a problem then.
No problem with the geometry. Thought there might be a special function built in.
I think there is a logic to it. Pi=180°.
You can get everything out of it.
Greetings.
When compiling, if OrderOpen(), OrderClose(), etc. functions are not checked, it gives a warning about this. Is there any point in writing this check if errors are logged anyway?
Greetings.
When compiling, if OrderOpen(), OrderClose(), etc. functions are not checked, it gives a warning about this. Is there any sense in writing this check if errors are already printed in the log?
A good "tone" of programming is a program without errors and warnings, everything else is amateurish.
Greetings.
When compiling, if OrderOpen(), OrderClose(), etc. functions are not checked, it gives a warning about this. Is there any point in writing this check if errors are logged anyway?