Discussion of article "MQL5 Cookbook: Developing a Multi-Symbol Volatility Indicator in MQL5"

 

New article MQL5 Cookbook: Developing a Multi-Symbol Volatility Indicator in MQL5 has been published:

In this article, we will consider the development of a multi-symbol volatility indicator. The development of multi-symbol indicators may present some difficulties for novice MQL5 developers which this article helps to clarify. The major issues arising in the course of development of a multi-symbol indicator have to do with the synchronization of other symbols' data with respect to the current symbol, the lack of some indicator data and the identification of the beginning of 'true' bars of a given time frame. All of these issues will be closely considered in the article.

We will get values of the Average True Range (ATR) indicator already calculated for each symbol based on the handle. For illustrative purposes, there will be six symbols whose names can be set in the external parameters of the indicator. The names entered will be checked for being correct. Should a certain symbol specified in the parameters not be available in the general list, no calculations will be made for it. All the available symbols will be added to the Market Watch window, unless they are already available there.

In the previous article entitled "MQL5 Cookbook: Indicator Subwindow Controls - Scrollbar" we already talked about the canvas on which you can print text and even draw. This time, we are not going to draw on the canvas but we will use it to display messages about the current program processes to let the user know what is happening at a given point of time.

MQL5 Cookbook: Developing a Multi-Symbol Volatility Indicator in MQL5

Author: Anatoli Kazharski

 
Anatoly, thanks for the article. Very interesting approach to volatility. I have learnt new ideas :-)
 

Hi,

I think you need to re-base the numbering for the yen pairs. The EURJPY pair has an ATR around 2, which shrinks the other pairs so you cant read them. Try dividing the ATR on the yen pairs by 10.

 
Looking good :)
 
Thank you very much for the article, I found exactly what I was looking for in it, and thank you MQ for covering such subtle topics as multi-currency analysis.
 

Great, but I have this picture in tester and real even after shiftbars was set manually and the indicator was changed to calculate by PRICE_CLOSE, below yours:

scratch

I have one negative from using MT lately, and that is the glitchiness of using standard indicators in multisystems, they just don't work. I have spent far too much time trying to work out that this is not the fault of any crooked hands. With the latest updates it gets worse and worse. Probably the masters are counting on the fact that fools from desperation will use a couple of mashka on this miracle to merge from nothing to do.

 
M1k3:

Great, but I have this picture in the tester even after shiftbars was set manually, below yours:

...

I have one negative from using MT lately, and that is the glitchiness of using standard indicators in multisystems, they just don't work. With the latest updates it gets worse and worse. Probably, the masters are counting on the fact that fools will use a couple of mashka on this miracle in desperation in order to merge from nothing to do.

I have not even tested this indicator in the tester in this form. It has a lot of unnecessary things for a tester. The article does not say anything about it either.

I haven't noticed any problems in using indicators in the tester from other symbols and timeframes, if you get their data from the Expert Advisor.

It is necessary to figure it out. I don't have an answer yet.

 
Manuel I could write to you privately this is my email st.co1258@gmail.com thank you very much
 
Anatoli Kazharski #:

... volatility ... true bars ...

it's not quite clear what the article is talking about ?!
... it's about volatility readings (ATR) from different TFs (by some key bars) - on the current TF (?!).

and under "true bars" - probably (if I understood correctly) - it means - opening bars on different TFs (??)
for example: True Bar with TF m15 , having opening time xx:15 min , xx:30 min (?!).