(Still not fixed in build 613. No response from Service Desk... 8 days and counting.)
vabz2014:
(Still not fixed in build 613. No response from Service Desk... 8 days and counting.)
What is your ticket number ?
(Still not fixed in build 613. No response from Service Desk... 8 days and counting.)
angevoyageur:
What is your ticket number ?
#959802
What is your ticket number ?
Looks as though it may have been fixed in build 614. Still no response from Service Desk, however.
I think that they may have done a quick fix of this by doing a complete reload of the EA when the timeframe changes. In v509, a static or global variable keeps its value if the EA is re-initialised by changing the timeframe or symbol. In v614 the variable is reset, implying that the EA is being reloaded from scratch. (I can't remember now, but I think that this was perhaps the behavior in versions of MT4 < 500.)
Thank you. Fixed.
Wait for the next build please
v616 seems to behave the same way as v509. The bug described above is no longer present, as in v614, with the further change that static and global variables are no longer reset when changing the timeframe of an EA (like v509, but unlike v614).
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
In the following example code, the glbLastServer variable is corrupted if an EA is reloaded by changing the chart timeframe. The EA should log one change of the value of glbLastServer, from a blank string to the name of the broker server. Instead, after being reloaded, it logs continual changes, with the value of glbLastServer being corrupted by the value of the implicit cast of the number 123456 to a string.
The following version does not seem to be affected: replacing AccountServer() with some other function which returns a string: