Discussing the article: "Developing a Replay System (Part 68): Getting the Time Right (I)"
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 68): Getting the Time Right (I).
Today we will continue working on getting the mouse pointer to tell us how much time is left on a bar during periods of low liquidity. Although at first glance it seems simple, in reality this task is much more difficult. This involves some obstacles that we will have to overcome. Therefore, it is important that you have a good understanding of the material in this first part of this subseries in order to understand the following parts.
If you prefer not to compile and test this service in MetaTrader 5, no problem. In the video below, I demonstrate how the service behaved and whether this test code is viable for use in the replay/simulation service. In my assessment, the test worked exceptionally well. It proved both the ability and feasibility of integrating the tested mechanism into the replay/simulator application. This would allow us to maintain accurate time tracking, even during low-liquidity periods or with symbols having low trading activity, ensuring users are informed of how much time remains before a new bar appears on the chart.
To integrate the tested mechanism into the replay/simulator application, we'll need to slightly modify a very specific section of the code. This section is located in the header file C_Replay.mqh. But before we move on to implementing those changes, there's another concept we need to understand first. To better organize the explanation, let's move on to a new topic.
Author: Daniel Jose