Errors, bugs, questions - page 1157
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
Clarifying the question - the progress should work in the indicator. Your code, when transferred to the indicator, stops displaying the comment at runtime.
To clarify the question - progress should work in the indicator. Your code, when transferred to the indicator, stops displaying the comment at runtime.
From the MQL4 help:
Running programs
A brief summary of MQL4 programs is shown in the table below:
Program
Execution
Note
Script
In its own thread, as many scripts as there are execution threads for them
A looped script cannot interrupt the work of other programs
Expert
In its own thread, as many experts - as many execution threads for them
A looped expert cannot disrupt work of other programs
Indicator
One execution thread for all indicators on one symbol. As many symbols with indicators - as many execution threads for them
An infinite loop in one indicator will stop all other indicators on this symbol
If the indicator is looped, the entire terminal can be "hung". But the Expert Advisor allows making fun of the flows as you want.
Well, the fact that an indicator can hang the terminal is a shortcoming of the terminal itself. And the analytical calculations, not related to trading, should be in the indicator - especially as it requires visualisation of buffers, i.e. it is not a task for the script either.
There's nothing looped in the indicator - in the sense that there's no infinite loop. There is a controlled calculation but it takes time.
...
Nothing is looped in the turkey - in the sense that there is no infinite loop. There is a controlled calculation, but it takes time.
In which indicator function call do you perform the calculation?
So how, after all, do you use the console compiler if it is removed by the terminal?
Why is it in the terminal? The terminal has all its own.
Just keep the compiler elsewhere.
Why is it in the terminal? The terminal has all its own.
Just keep the compiler elsewhere.
Yes, it's understandable that the way out is to keep the compiler in a different folder than the terminal one. But the fresh *.ex5 files won't be created in the terminal folder either, which means that they must be constantly moved to the right place... Although, could there be a command key to specify the path of the compiled files?
Yes, you can specify a default directory in the /i key: