Errors, bugs, questions - page 1044
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
https://www.mql5.com/ru/docs/constants/environment_state/marketinfoconstants
SYMBOL_SESSION_PRICE_SETTLEMENT
Supply price for the current session
Question why all variables in help do not correspond to their names in the terminal)
Could you please tell me if an EA designed for 4-digit quotes can work on 5-digits?
Please tell me if an EA developed for 4-digit quotes can work on 5-digit ones?
Yes it will work (most likely), just zeros will be assigned to the fifth digit, but the opposite is more difficult, if there is no special gearing it may fail due to the roughness of the calculation.
But we should check the logic and see if there are constants instead of calculations, and then the first option might not work, depending on the diligence of the programmer.
Could you please tell me if an EA developed for 4 digits can work on 5 digits?
Could you please tell me if an EA developed for 4-digit quotes can work on 5-digits?
Have a look at the five-mark examples of the MACD Sample Expert Advisor
The Expert Advisor was developed a long time ago and is designed for 2 or 4 signs. In 5, it was tuned for 3 or 5 digits. The m_adjusted_point variable is responsible for this
Slava, what are the new trends with zeroing in calculators prev_calculated on every tick ?
How long will it last?
The processing scheme of prev_calculated / rates_total was supposed to be economical.
And what do we have now? :
Two or three calls of OnCalculate(...) at every tick and the last one requires recalculating indicator completely from zero.
My room is already "tachkent" - video card is overheating (calculating a bunch of heavy indicators in OpenCL).
--
How to live?
Slava, what are the new trends with zeroing in calculators prev_calculated on every tick ?
How long will it last?
The processing scheme of prev_calculated / rates_total was supposed to be economical.
And what do we have now? :
Two or three calls OnCalculate(...) on every tick, the last one requiring full recalculation of indicator from scratch.
My room is already "tachkent" - video card is overheating (calculating a bunch of heavy indicators on OpenCL).
--
How to live? NadaCalculate!
About a month ago this issue already came up. We have not been able to reproduce this problem in our
Don't you have calls of this indicator from the Expert Advisor?
This issue already came up about a month ago.
1) We have not been able to reproduce this problem with ourselves
2) Do you have any calls of this indicator from Expert Advisor?
2) There are no calls from the expert
1) I will help :)
In the trailer you can enable/disable calling of CopyRates() and writing of values in buffer.
In "empty" variant (as you probably checked) it works according to specification (prev_calculated on each tick is not zeroed and called once).
But "under load" (when copying/writing values) it starts messing around.
Check it: