First, pardon me perpetuating the issue. I have a lot to learn.
By consensus of this thread and other doco, it seems to me the "repaint" issue is real when backtesting visually, but not when trading live.
But visual backtesting is commonly enough done that it's a sticking point for some of us including me.
The TMA slope indicator will cough repaint 20 bars back. See the first attachment for a strident example. It shows an M1 chart over the weekend gap.
repaint vs no repaint.gif
As it appear looking back with the normal TMA slope (first indicator), it indicated that things were going down 20 bars before the market closed. The second indicator is my first attempt at a non-repainting TMA slope, which shows an expected spike down in the TMA slope corresponding to the open gap down. Ignore the third indicator - that's a work in progress.
We can fix this. We can make the indicator not repaint. I've half done it; it works in "realtime" - once you apply it to a chart, every bar after that does not repaint. But it's not working for history yet. That is, if we apply it to a chart with bars in the past, no histogram is drawn for that. I'll look into that; I can't see why it can't be solved.
The second attachment just shows historically what a difference it makes. Again the top indicator is the unmodified TMA Slope and the second is the non-repainting version.. Again, look back, the TMA slope is brilliant, picking the movements
seemingly before they happen. The realtime reality is somewhat different. It indicated "up" 14 bars later than the unmodified TMA slope, and had a false positive a bit later, that the unmodified one had erased.
repaint vs no repaint 2.gif
My point: if it's a big enough stumbling block, and we can fix it, then perhaps we should.
This is not a criticism of 10.2 or NB.
Tony
You do not have the required permissions to view the files attached to this post.