![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
Correct, it is calculated. The cell number is found. From this cell (time series) the value of maximum or minimum of the bar is taken. It is considered that the maximum has been found on this bar. This value is then placed in the indicator buffer with the found number. The maximum of the indicator should correspond to the maximum on the bar. In my code, maximum is also taken from the array (timeseries) with the same found number and compared to the value of val. It is checked to see if we are doing the right thing: we put into the buffer with this number the value of val. It should also be equal to the maximum of the bar. Comparison of numbers taken from the same place is quite correct.
It seems to me that comparison ...==val, is dangerous because it is the cell number that may change from tick to tick. Especially at small timeframes where there are a lot of closely matched Low and High. However, we should think it over, maybe we mean different moments.
Please note that although the parameter names are retained, they work differently.
Please keep in mind that although the names of parameters are the same, they work differently.
Candid. I will have a look at it. The first time I installed it, I had the following observation.
There are several consecutive bars with the same highs. Your variant of the zigzag draws the break (top) on the last bar. That is, the bar closest to zero. Ideally, the break should be drawn on the first bar, which is farthest from the zero bar. The first vertex that appears is significant. It's the same with mtnemums. I can cite several sources (from the literature), where it is required to do so.
Yes, I noticed :) just an idea :) . I am now using my ZZ all over the place (code in the post above) It works more stable with other TF data.
On the first installation, the following observation immediately arose.
There are several consecutive bars with the same highs. Your zigzag option draws a break (top) on the last bar.
Klot, interesting option.
If your zigzag variants show interesting results, can I apply them in my development?