Discussing the article: "Developing a Replay System (Part 69): Getting the Time Right (II)"

[MetaQuotes]

Check out the new article: Developing a Replay System (Part 69): Getting the Time Right (II).

Today we will look at why we need the iSpread feature. At the same time, we will understand how the system informs us about the remaining time of the bar when there is not a single tick available for it. The content presented here is intended solely for educational purposes. Under no circumstances should the application be viewed for any purpose other than to learn and master the concepts presented.

In the previous article, "Developing a Replay System (Part 68): Getting the Time Right (I)", I explained the portion of code related to the mouse indicator. However, that code has little value unless you also examine the code for the replay/simulator service. In any case, if you haven't read the previous article, I recommend doing so before trying to understand this one. This is because one truly complements the other.

The focus here, for now, is on providing information about the remaining time on the bar when the asset is experiencing low liquidity. This may happen due to the absence of traditional generation of OnCalculate events during such periods. Consequently, the mouse indicator will not receive the correct values corresponding to the elapsed seconds. However, based on what was covered in the previous article, we can indeed pass the necessary values so that the indicator can calculate the remaining seconds.

Demo video

Author: Daniel Jose