Discussing the article: "Developing a Replay System (Part 64): Playing the service (V)"
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
Check out the new article: Developing a Replay System (Part 64): Playing the service (V).
In this article, we will look at how to fix two errors in the code. However, I will try to explain them in a way that will help you, beginner programmers, understand that things don't always go as you expect. Anyway, this is an opportunity to learn. The content presented here is intended solely for educational purposes. In no way should this application be considered as a final document with any purpose other than to explore the concepts presented.
In the previous article, Developing a Replay System (Part 63): Playing the service (IV), we developed and implemented a mechanism to allow users to adjust the maximum number of ticks that will be used to construct a bar on the chart. Although the primary purpose of this control is to ensure that bar construction does not interfere with other critical areas of the replay/simulator application, it does not affect or distort the actual volume values that should be displayed.
However, if you paid close attention to the video in that article or compiled and tested the replay/simulator application yourself, you might have noticed that, from time to time, the system would unexpectedly enter pause mode. Strangely enough, this happened without the control indicator reflecting any change. It wasn't clear why we somehow transitioned from play mode to pause mode. I admit, it's indeed quite odd. You're likely wondering how such a thing could happen. In fact, I asked myself the same question, trying to understand why the system was pausing, and always at specific points. With that said, the next section will explain the solution I developed and how the problem can be understood.
Author: Daniel Jose