Some indicators should be exclusively used in CalculateOnBarClose = true setting, as

- the algorithm used may not be compatible with CalculateOnBarClose = false

- or the CPU load would be too high


A very brute way to achieve this would be to start OnBarUpDate() with the code snippet

 

Code

if (!CalculateOnBarClose) return;

and the indicator will display nothing with the false settings.


But is there anything more elegant, such as eliminating CalculateOnBarClose from the indicator dialogue settings?

Fat Tails 

Some indicators should be exclusively used in CalculateOnBarClose = true setting, as - the algorithm used may not be compatible with CalculateOnBarClose = false - or the CPU load would be too high A very brute way to achieve this would be to start OnBarUpDate() with the code snippet   Code if (!CalculateOnBarClose) return; and the indicator will display nothing. But is there anything more elegant, such as eliminating CalculateOnBarClose from the indicator dialogue settings?

You could force the issue in OnBarUpdate, thereby ignoring what the user selects.

 

Code

if (!CalculateOnBarClose) CalculateOnBarClose = true;

Mike

comment it out ( // CalculateOnBarClose) - this should work.
i saw this in indicators yet.

if it is faster then, i dont know.

max-td 

comment it out ( // CalculateOnBarClose) - this should work. i saw this in indicators yet. if it is faster then, i dont know.

If I comment it out it will just be ignored but not compensate a false user setting.

Honestly, I don't undertstand this answer.

Big Mike 

You could force the issue in OnBarUpdate, thereby ignoring what the user selects.   Code if (!CalculateOnBarClose) CalculateOnBarClose = true;  Mike

Will try that, if it works, it is a good solution.

NT users are by now already used that is not up to them to select the features, so nobody will complain about it.

Fat Tails 

Will try that, if it works, it is a good solution. NT users are by now already used that is not up to them to select the features, so nobody will complain about it.

Sure. If you are really kind, you could throw an Alert letting the user know you changed it and why.

Mike