Best practice calling base.OnBarUpdate()

[neoikon]

I can't seem to find a clear answer so I thought I'd ask. For Indicator development (and Drawing Tool development, if it matters) what are the best practices for calling base.OnBarUpdate() (within OnBarUpdate())?

Sometimes I see "base.OnBarUpdate()" called and sometimes not. Is it required? Always first thing within the function? What circumstances do you want to or not call it? I want to make sure that I'm not causing a performance hit, by it being called twice (once behind the scenes and once by my explicit call).

It seems that base.OnRender() is necessary for things like the Plots to function properly, which would imply that calling base.OnBarUpdate() would be necessary in some situations too.

(obviously, I'm referring to calling them within their appropriate OnBarUpdate() or OnRender() locations)

Thank you and stay safe!

[NinjaTrader_Jesse]

Hello neoikon,

Thanks for the post.

Calling base.OnBarUpdate is not necessary, however that may be related to those specific items and how they were developed. Any items you create should not need that. It is also possible they used visual studio and had used a plugin like resharper to generate overrides, that would include base.OnBarUpdate in that use case but its still not needed that is just a normal feature of syntax generation for C# overrides.

The OnRender override does have base logic so calling base.OnRender can be used logically to either render the plots or not. The pivots uses this in its logic to custom plot.

For any override method which is a virtual override you don't necessarily need to call the base, that depends if the base has any logic which that would execute. OnRender is the only override that I can think of that has some base logic which actually would affect your end result, there could be others but they are not any of the common overrides.

I look forward to being of further assistance.