Thanks Mladen and yes the code reminded me of some of those decompiled files !
I found this Trix combo to be helpful but it repaints. I changed the "for (i = limit......." lines as you suggested earlier but it still repaints, Line # 189 seems suspicious?? Can you help straigthen this indicator and its alarms out???
I wish that it was that simple (one line problem)
Not going to explain all the things wrong in that indicator (wrong arrays coding, missing signals, ... ) so decided to make a new one. In order to get signals as it is intended in the one you posted set the Trix period to 3 and signal period to less than 2 (in that case the indicator effectively checks for 0 line crosses, if you set the signal; period to greater than 1 it will check for signal line crosses, so, by setting signal period you choose which kind of a signal you want)
The rest of parameters are more or less usual. As comparison : see where some signals are missing (so not repainting, but plain missing) Dots are drawn by the new one, and the lower is the "Scalper" just adjusted to show values of trix (so where it should have signaled)
I noticed the pivot point indicator you made is doing something strange on the AlpariUS chart for Daily Pivots. For some reason Monday's reading goes off the chart when you set the TZ to 1 for the AlpariUK TZ.
Would you mind looking at this for me?
It works Great!! I love the signal options. I changed the setlabel to identify the signal type but don't know how to change the color, please see line # 80, can you help me ??
I thought that I posted the version that does have a Sunday fix feature but it seems that I was wrong .
Here is a version that does fix Sunday data (it actually skips that funny 1 or 2 hour data Sunday usually has, and, if used, gives completely wrong pivot points. Alpari does not have that Sunday data, but with time shift added, all of a sudden it artificially starts to have it (time from Monday 00:00 to 01:00 becomes Sunday with hour shift set to 1) and that is causing that error)
But if you set the hour shift to 1 and turn the FixSundays to false, you are going to get the same thing as before (for reasons I have explained above) So it is much safer to use FixSundays and ignore any eventual Sunday data all the time
Updated version posted here : https://www.mql5.com/en/forum/general
lol...no worries. I remember you mentioning it.
this is great! thanks a lot!
Here is a version that does fix Sunday data (it actually skips that funny 1 or 2 hour data Sunday usually has, and, if used, gives completely wrong pivot points. Alpari does not have that Sunday data, but with time shift added, all of a sudden it artificially starts to have it (time from 00:00 to 01:00 becomes Sunday with hour shift set to 1) and that is causing that error)
This should do it
PS: default time frame is weekly, but you can choose other time frames with this one (so, it is not just a weekly indicator)
Range = high - low;
H4 = close + (Range * 1.1/2.0);
H3 = close + (Range * 1.1/4.0);
H2 = close + (Range * 1.1/6.0);
H1 = close + (Range * 1.1/12.0);
L1 = close - (Range * 1.1/12.0);
L2 = close - (Range * 1.1/6.0);
L3 = close - (Range * 1.1/4.0);
L4 = close - (Range * 1.1/2.0);
Thanks so much to anyone who might help.
Jurik cci with bands, mtf,arrows and alerts
updated version here: https://www.mql5.com/en/forum/general
Jurik smoothed Trend Score.