ter. . .after searching a bit longer....
Or is here anyone who has made other adventures?
ter. . .after searching a bit longer....
Or is here anyone who has made other adventures?
//--
hey reteid.... Not sure just what aspect of those functions your speaking too.... ihighest and ilowest can mislead some systems....
Because you understand, but others may not, ihighest and ilowest worth isn't immediately set in stone like iclose.... So there is the lookback time period where it is worth is subject to change.... So it is itime is subject to change....
When the system can make adjustments for that, it is no problem....
Zigzag is a great example...h
I never confronted problems with these purposes in my progr. Maybe it is not simple to us the right pub and range in certain situations but if used properly it works without errors.
Do you have an example how to utilize them?
I really don't see a problem with this either. One way would be to figure out the H1 from the corresponding M5 candles. The easy way I to alter the bar on the view timeframe (M5) to the calculation timeframe (H1) and use the bars of this calculation timeframe.
I think you use the first approach because that is the only reason to use iHighest und iLowest. One silly question you know this function results are noth that the higest/lowest value they provide you with the index in the array where the barhas highest high or lowest low?
I don t understand what has been calculated. . .but not the correct values. . .so I wrote my own one:-)