Discussing the article: "Developing a Replay System (Part 76): New Chart Trade (III)"

[MetaQuotes]

Check out the new article: Developing a Replay System (Part 76): New Chart Trade (III).

In this article, we'll look at how the code of DispatchMessage, missing from the previous article, works. We will laso introduce the topic of the next article. For this reason, it is important to understand how this code works before moving on to the next topic. 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 75): New Chart Trade (II), I explained several aspects of the C_ChartFloatingRAD class. However, because the material was quite dense, I aimed to provide the most detailed explanation possible whenever relevant. One procedure remained to be discussed. Even if I had left it in the header file C_ChartFloatingRAD.mqh and tried to explain it in the previous article, it would not have been adequate. This is because, to fully understand how the DispatchMessage procedure works, another topic needs to be explained alongside it.

In this article, I will be able to go into detail about how the DispatchMessage procedure truly operates. This is the most important procedure of the C_ChartFloatingRAD class, as it is responsible for generating and responding to the events that MetaTrader 5 sends to the Chart Trade.

The content here should be read in conjunction with the previous article. I do not recommend taking on this article without first thoroughly grasping what was covered before. Together, the last two articles and this one represent the full conceptual foundation behind the Chart Trade indicator. Therefore, it is important to understand each of them.

Author: Daniel Jose