Hi mladen, I've tested your indicator and since now it seems to me that it doesn't repaint.
Do you confirm my impression?
Hi mladen, while I wrote to you I've noticed that an arrow has appeared in the attached chart at 9:10GMT(11.10 server time that I use) but no alert was found in my mt4 terminal as you can see below (from 11:06 till now no signal). May you check some problem in the alert indicator? (my settings are alert only on candle close, not current)
SSA recalculates (unless it is a end-point version). If the arrow was drawn (repainted) further in the back than the alert required bar, then the arrow is going to be drawn but the alert is not triggered
MLADEN. thanks for youe explanation. There is a end-point version of this indicator , or is it possible to have a version end-point?
End point version looks completely different as far as values are concerned
Could you please change this indicator to HISTO VERSION
Mladen, Could you create an histo version of this indicator averages MTF alerts 7_8 because I use histo? Have a nice weekend.......
Simple things can make much difference, atleast try if you get time from your busy schedule. Thanks
It goes more or less like this :
- If the built in macd is used, the regardless of the displayed bars, all the bars are calculated and then on new ticks, only those 1,2 or 3 are are calculated
- if some custom macd is used, then if not enough bars are calculated, the risk of having wrong current macd value rises. So, in order to have correct values, as much as possible past values have to be used in order to provide as correct as possible current value, and then it would do the same : on new ticks, only last 1,2 or 3 bars are calculated making the calculating CPU time on new ticks neglectable (the same as any other correctly coded indicator)
So, all in all, with correctly coded indicator, adding bars limitation : raises the chance of error, and adds unnecessary code to code execution and macd calculation
I can confirm works well now under El Capitan OS and Windows10 Pro!