altoronto: Mladen, whenever you have time can you explain me how this works as far as I can see its uses 3 Smoothed Moving Averages (3,2,1).
Thank you in advance.
And it uses a "hidden" average too (when it calculates the HL values)
The problem with that indicator is that it uses the variables that are visible on a global scope in a wrong way (some other indicators have same error like that : when they assume that it is always the first tick of the calculation) That error would require a total indicator rewrite before being able to see what is the exact logic
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
That one is easy to make non repainting. Here is the non-repainting version
Thanks, it is OK now
This repaint 8 bars back
This repaint 8 bars back
That one can not be made non-repainting
That one can not be made non-repainting
I see. Thanks
Does not repaint but shows the cross at a wrong bar
Does not repaint but shows the cross at a wrong bar
You can use a simple ma cross indicator instead of that one (here is one : https://www.mql5.com/en/forum/173235/page60 that works OK)
It is saying "Cycle identifier" in the code - so it repaints
FTS alert indicator - repaints
FTS alert indicator - repaints
Mladen, whenever you have time can you explain me how this works as far as I can see its uses 3 Smoothed Moving Averages (3,2,1).
Thank you in advance.
Mladen, whenever you have time can you explain me how this works as far as I can see its uses 3 Smoothed Moving Averages (3,2,1). Thank you in advance.
And it uses a "hidden" average too (when it calculates the HL values)
The problem with that indicator is that it uses the variables that are visible on a global scope in a wrong way (some other indicators have same error like that : when they assume that it is always the first tick of the calculation) That error would require a total indicator rewrite before being able to see what is the exact logic