CC,
Inside the indicator, in user inputs, it has these inputs:
int GrossPeriod=60;
int GrossPeriod2=240;
int GrossPeriod3=1440;
The GrossPeriods are obviously Timeframes. Then in init function we see further code:
if(Period()==60){GrossPeriod=60; GrossPeriod2=240;GrossPeriod3=1440;}
if(Period()==240){GrossPeriod=240; GrossPeriod2=1440;GrossPeriod3=10080;}
if(Period()==1440){GrossPeriod=1440; GrossPeriod2=10080;GrossPeriod3=43200;}
if(Period()==10080){GrossPeriod=10080; GrossPeriod2=10080;GrossPeriod3=43200;}
H1 is the ONLY timeframe I'm looking at. I was going to - at first - try to make this system for scalpers also, but I since decided against this idea, and to stick with what you use, which was said to be H1).
So if you are on H1, then per above code in init, GrossPeriod = 60 (these Semafors are turned to none/black in your template), GrossPeriod2 = 240 (these Semafors are turned to white in your template), and GrossPeriod3 = 1440 (these Semafors are turned to magenta in your template). So if using H1, the H1 Semafors are not seen, the H4 are white, and the D1 are pink. This is per code in ATeam.
if you are on H4, then per above code in init, GrossPeriod = 240 (these Semafors are turned to none/black in your template), GrossPeriod2 = 1440 (these Semafors are turned to white in your template), and GrossPeriod3 = 10080 (these Semafors are turned to magenta in your template). So if using H4, the H4 Semafors are not seen, the D1 are white, and the W1 are pink. This again is per code in ATeam.
This is how the indicator is set up, and calls an indicator named "ZigZag2", which we don't have in indicators folder, although we do have "Zigzag2". So the fact that we get any values at all is a complete conundrum to me.
Now, if you'd like, since I'm now using CountZZ function, having discarded hope of using iCustom in any capacity for Semafor information since there are multiple pairs and timeframes, I can put in any timeframe you want. Just let me know. I can put them all in if you want.
Also, there is a big difference here in what is needed visually and what is needed in code. For me to see Semafors MTf on same chart, visually what's needed I guess as long as not many charts ATeam indicator. It calling iCustom to the wrong iCustom or any iCustom is not the best way to go IMHO like it's coded.
But if I'm getting info for indicator like mine, or EA, I don't need "MTF" code for Semafors. If I want MN1 Semafor, I call e.g. iCustom(Symbol(), PERIOD_MN1,"custom indi name",inputs,...,buffer,shift = 0);
I would NOT call it from this timeframe like e.g. iCustom(Symbol(), PERIOD_H1,"custom indi name",input for higher timeframe, other nputs,...,buffer,shift = 0);
I'm not saying there are not instances where I ca;; MTF indicators. Unlike most coders, I do see a need sometimes for MTF indicators and calling them. So I don't just default to the first type of iCustom line seen above, but in this case, it's best (not to call MTF indicator and just call regular indicator on higher timeframe or, as this is slowing Empty4 to a crawl/locking up, implement indicator code directly into the EA code (which is what my indicator code will become, so I code the indicator as if I am coding an EA, since that's the destination, so don't use Bars variable for instance).
I hope I've made myself clearer than mud
Kindest regards,
Don