Discussing the article: "Developing a Replay System (Part 67): Refining the Control Indicator"
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 67): Refining the Control Indicator.
In this article, we'll look at what can be achieved with a little code refinement. This refinement is aimed at simplifying our code, making more use of MQL5 library calls and, above all, making it much more stable, secure and easy to use in other projects that we may develop in the future.
In the previous article "Developing a Replay System (Part 66): Playing the service (VII)", we implemented a method to determine when a new bar would appear on the chart. Although that method works very well for models with good liquidity, it is by no means suitable for use with low-liquidity models or those frequently subject to auction halts. This type of issue will be resolved in the near future.
However, here I would like to show you something else. This is equally interesting, although it doesn't make much of a difference for users who are only interested in using the application. For those users, what I begin exploring at the start of this article is of little relevance. But for those who are studying and truly aiming to become a skilled programmer, what I'll show next makes a significant difference. It impacts both how you write code and how you read your own code as well as that of other developers. Indeed, we can learn a great deal by observing how others approach problem-solving through code. Even problems that are somewhat related can be implemented in completely different ways, depending on the developer. Or even by the same developer revisiting and refining their approach in a given language.
Author: Daniel Jose