Discussion of article "MQL5 Programming Basics: Time" - page 3
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
The article is actually harmful, because it 1 to 1 reiterates the MQL5 documentation and says nothing about the practice of working with time.
and for this kind of code in production
programmers are deprived of their bonuses.
PS. The most popular questions - "what time is it in Greenwich", "how long ago was the tick just received generated", "is it time to postpone calculations so as not to miss something?
The article is actually harmful, because it 1 to 1 reiterates the MQL5 documentation and says nothing about the practice of working with time.
and for this kind of code in production
programmers are deprived of their bonuses.
PS. The most popular questions - "what time is it now in Greenwich", "how long ago was the tick just received generated", "is it time to postpone calculations so as not to miss something?
Will you be personally taught to read to see in the article about practice?
aStartDay*86400+3600*aStartHour+60*aStartMinute; - this is not production, but a training code for a training article, for quick visual understanding.
1 second has no duration?
No further questions: ))))))))))))))))))))))))))))))
Will you be personally taught to read to see in a practice article?
aStartDay*86400+3600*aStartHour+60*aStartMinute; - this is not a production, but a training code for a training article, for quick visual understanding.
Ehh... you don't even realise how bad this "training code" is :-(
PS. I will not teach you how to write it personally.
Ehh... you don't even realise how bad this "training code" is :-(
PS. I will not personally teach you how to write.
Topics that get the crowd going:
1. God.
2. Infinity.
3. Absence of line thickness and point size in geometry.
4. Absence of duration of a moment in time.
5. When someone does something better than you.
6. When someone is just good at doing something.
7. When someone has done something.
Momentum doesn't, and a moment is not a second. You're the one who has a moment equals a second.
Mm-hmm.
In your example, the code is executed at a certain second, but not a moment.
Mm-hmm.
In your example, the code is executed at a certain second, but not a moment.
The time of the moment is specified to the nearest second. But the moment itself has no duration.
Let's assume that ticks occur at a frequency of 10 times per second. If you use the code for an interval, several ticks will be skipped. If you use the code for a moment, only one trigger will occur, no matter how often the ticks occur. It is checked that one tick was before the specified time, and the second tick was at that time or later. Time boundary crossing.
They used to be. They fell off somewhere. Probably during some server update.
I'm going to look for them, and if I find them, I'll attach them here.
The question is in the context of the topic...
I need an analogue of TimeCurrent() with millisecond accuracy, something like TimeCurrentMsс().