Discussing the article: "Market Simulation: Position View (XIX)"

[MetaQuotes]

Check out the new article: Market Simulation: Position View (XIX).

One of the issues that bothered me the most was that the `C_ElementsTrade` class contains code for accessing positions. Don't take this as a mistake, because it really isn't one. However, this increases the risk of errors in some of the tasks we will need to handle later. All work on implementing the position indicator was carried out with a view to its use in the replay/simulation service. However, when running in this environment, we will have no access to actual positions. Consequently, any call to the MQL5 library intended to retrieve position data will have no effect in this environment.

In the previous article “Market Simulation: Position View (XVIII),” I showed how to solve some problems. For example, I explained how to prevent a user from deleting graphical objects created by the position indicator. We did this very simply, without any major complications, since restoring the objects in the correct order can be quite time-consuming and require some real programming acrobatics from us. In addition, we added a volume display—data that some traders use to determine whether a particular strategy can be applied to a position.

This information allows you to make an informed decision to increase a position that is already profitable or to reduce risk. If you are holding a significantly large volume, a market movement in the direction opposite to your position could result in a very large loss. This often results in the risk ultimately closing the trade, and shortly afterward you see the market moving in the direction you had anticipated. Not only is this a very unpleasant situation, but it also has a serious psychological impact on the trader and causes them to completely lose confidence in themselves.

All of this was implemented quite simply and with very few changes to the existing code. I hope you're following along and seeing that it's not really that complicated. We just need to calmly analyze each situation before making changes to the code. Depending on the situation, a small change in how a particular part of the system is implemented may be more than enough to solve a specific problem.

Now, however, we need to tackle a somewhat more complex issue, one that I have been putting off for quite some time. Don't think the work will be extremely difficult. You will see that, although the problem is somewhat complex, I will explain it simply and clearly. All right, let's get down to business.

Author: Daniel Jose