Discussing the article: "Developing a Replay System (Part 57): Understanding a Test Service"

MetaQuotes 2025.02.04 06:28

Check out the new article: Developing a Replay System (Part 57): Understanding a Test Service.

One point to note: although the service code is not included in this article and will only be provided in the next one, I'll explain it since we'll be using that same code as a springboard for what we're actually developing. So, be attentive and patient. Wait for the next article, because every day everything becomes more interesting.

In the previous article Developing a Replay System (Part 56): Adapting the Modules, we made some changes to both the control indicator module and, most importantly, the mouse indicator module.

Since the article already contained quite a lot of information, I decided not to add any more new data, as it would most likely only confuse you, dear reader, instead of helping to clarify and explain how things actually work.

The attachment to the previous article contains the mouse indicator and the service. When you run the service, it will create a custom symbol and will add a panel with a mouse indicator and a control indicator. Both modules are placed on the custom symbol chart, and although they do not perform any service related actions, some interaction activity can be seen between the user and these two modules.

You may not have any idea how to do this, especially if you are new to MQL5. If you look at the code of these two indicators, you may not see any activity that would prevent the loss of data present in the indicator, or more precisely, in the control module.