Dashboard TZ

Quoting braintheboss

Disliked

{quote} It's easy to explain. I don't know how icustom indicator detects new bars. But I think will use same logic than mine. If candle time is smaller than TF offset, will not detect new bar not processing it correctly. This can lead other problem. If you have 3 renko candles with time inside TF offset for Trend only will see one growing the problem. I can resolve this issue but I can't do it with icustom indicator I'm invoking The only solution is start renko times with 0 time and write every candle with a time >= TF candle duration. This solution...

Ignored

Quoting Hotpotato

Disliked

{quote} Does that make sense ? If i load Trend on a M2 (M19 for me) Renko chart with the same bars and same time stamps of course because they are in the.hst file, trend works. So if you read directly from the.hst file in both instances it is the same. Something strange happening.

Ignored

int OnCalculate(const int rates_total,
                const int prev_calculated,
                const datetime &time[],
                const double &open[],
                const double &high[],
                const double &low[],
                const double &close[],
                const long &tick_volume[],
                const long &volume[],
                const int &spread[])
  {
//---
    for (int i=0;i<28;i++) {
      if (iClose(allpairs[i]+"i",19,0) != oldbid[i]) {
         oldbid[i] = iClose(allpairs[i]+"i",19,0) != oldbid[i];
         Print(Symbol()+"  "+Period()+" tick received for "+allpairs[i]+" ima "+iMA(allpairs[i]+"i",[color=Red]19[/color],13,8,MODE_SMMA,PRICE_MEDIAN,0));  
      }
//         UpdateChartWindow(i);
   }  
//--- return value of prev_calculated for next call
   return(rates_total);

Quoting Hotpotato

Disliked

B, then your problem must be the iCustom. If i extend the "tick detector" running on the same chart as the trend server and i let it calculate the MA is works. int OnCalculate(const int rates_total, const int prev_calculated, const datetime &time[], const double &open[], const double &high[], const double &low[], const double &close[], const long &tick_volume[], const long &volume[], const int &spread[]) { //--- for (int i=0;i<28;i++) { if (iClose(allpairs+"i",19,0) != oldbid) { oldbid = iClose(allpairs+"i",19,0) != oldbid; Print(Symbol()+"...

Ignored

Quoting Hotpotato

Disliked

{quote} Does that make sense ? If i load Trend on a M2 (M19 for me) Renko chart with the same bars and same time stamps of course because they are in the.hst file, trend works. So if you read directly from the.hst file in both instances it is the same. Something strange happening.

Ignored

Quoting braintheboss

Disliked

{quote} Ok. I will try your way. Seem easy to add it without change all detector code {quote} I found the problem. I use bar date for detect new bars because its more reliable than iBars ( when you have missing history bars ). But with renko check bars count is more reliable. I dont read hst file. I use CopyRates and standard API work work with offline charts

Ignored

Quoting Hotpotato

Disliked

{quote} I can remember that somewhere you said that you read the .hst file but never mind. If that is the case than you probably also have solved the problem of Catalin and his "missing signals" (or to late). Multiple Renko bars can pas within one normal tf bar.

Ignored

Quoting braintheboss

Disliked

{quote} I read API but indicator inside Trend I think read hst. But I sent to Husky a new build. He will test fast. If works I will adapt server mode and I think will work fine

Ignored

Quoting Hotpotato

Disliked

{quote} Oke but husky hasn't got the no-chart=needed writer yet.

Ignored

Quote

Disliked

I read API but indicator inside Trend I think read hst. But I sent to Husky a new build. He will test fast. If works I will adapt server mode and I think will work fine.

Quoting Hotpotato

Disliked

{quote} Husky what is taking you so long ? I think i am going to bed.

Ignored

Quoting braintheboss

Disliked

{quote} Ok. Tomorrow I hope have good new for you

Ignored

Quoting Hotpotato

Disliked

{quote} I was joking. Not going to bed until this is solved.

Ignored

Quoting Hotpotato

Disliked

Just confirmed 19 minute wait before signals appear.

Ignored

Quoting braintheboss

Disliked

{quote} That is the shift in tick generated MA comparing with refreshed MA. Resolved that you have perfect entries

Ignored

Quoting Catalin68

Disliked

HP & BtB, I think this mix apples with pears and want something good to come out ... you said a little behind that Renko your not working with "time". I'm not good at programming, but I think TrendServer has this ingredient. I mean, I read TrendServer bars are not the same thing Renko bars. Probably so signals do not match ... not give the bat, is just an opinion.

Ignored