That is, in other words, this:
normally returns the proper server time for the last bar for the current period whichever it is; however it randomly returns "1970.01.01 00:00:00" for no apparent reason since none the Symbol(), nor the current period changed; then a few ticks later when a new bar was generated, it returns back to the correct server time.
It sounds pretty much like a bug, although maybe I'm not taking something into account. Any clue, anybody?
Hi Lucero,
Nope, no clues. Just a thought, did you set the number of Bars to unlimited ?. I set mine to 10,000 and no error on M1 chart.
:D
- www.mql5.com
We are investigating this behaviour. Please wait for a while.
Hi onewithzachy, thanks for the comment. I didn't try that, but I wouldn't think it's related since I wasn't myself changing the number of bars in between, other than when a new bar was generated. Right now I'm doing some other testings but I'll be keeping an eye on that when I get back to that testing, keeping in mind your suggestion.
Hi Alex, no prob. Frankly I'm not sure if I caused it myself accidentally somehow (though it didn't seem it was the case), right now I'm working on something else but I'll get back on this if I find anything relevant.
- www.mql5.com
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
That is, in other words, this:
normally returns the proper server time for the last bar for the current period whichever it is; however it randomly returns "1970.01.01 00:00:00" for no apparent reason since none the Symbol(), nor the current period changed; then a few ticks later when a new bar was generated, it returns back to the correct server time.
It sounds pretty much like a bug, although maybe I'm not taking something into account. Any clue, anybody?