Discussing the article: "Developing a Replay System (Part 55): Control Module"
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 55): Control Module.
In this article, we will implement a control indicator so that it can be integrated into the message system we are developing. Although it is not very difficult, there are some details that need to be understood about the initialization of this module. The material presented here is for educational purposes only. In no way should it be considered as an application for any purpose other than learning and mastering the concepts shown.
Until recently, the replay/simulator system used global terminal variables to provide some level of communication between programs needed to interact, control, and access the replay/simulator service.
Since we start using a module system where messaging is done through user events, we will no longer need to use global terminal variables. With this in mind, we can now remove all global terminal variables that were used previously. However, in this case, we will need to adapt the system so that information continues to flow between programs.
Modelling an information transmission system is a task that requires great attention and caution, since there is simply no possibility of reading the information later. If a program or application is not on the chart when information is received via a custom event, that information will be lost. Therefore, additional mechanisms are needed to resend the same information until we have confirmation that it was received by the intended application or program.
In the video below, you can see the system running.
Demo video
Author: Daniel Jose