I've discovered that doing different things in "CalcBar()" affects what is treated as 1st bar on a chart, or where the calculation of an indicator starts.

I have done some work on discovering what was the cause. For example, doing this...

Code: Select all

```
// Core Functions:
```

m_CF_curHigh = Bars.High[0];

m_CF_curLow = Bars.Low[0];

m_CF_preHigh = Bars.High[1];

m_CF_preLow = Bars.Low[1];

m_CF_curClose = Bars.Close[0];

Or this:

Code: Select all

```
p_PlotObject.Reset(55);
```

Code: Select all

```
if ( Bars.FullSymbolData.Current > Bars.FullSymbolData.Count - ( 288 + 55 ) ) Counter++;
```

The solution would be to force MultiCharts to start the calculation on the 1st bar every time.

Can this be fixed in the next upcoming version of MultiCharts?

Best regards,

Johannes Hillestad Baumann