But what about when an indicator calls another indicator. ?
For example ... blah = myJunkInd(123,456);
What I've found is that the "called indicator" will return null IF "CalculateOnBarClose=true; is coded on the called indicator. Even if the "Calling indicator" has CalculteOnBarClose = false. Ie, it does not over-ride.
Which makes for some pretty weird results !
The test cases I did on the 'called indicator' were ...
1 - CalculateOnBarClose not coded = Works as expected
2 - CalculateOnBarClose =false coded = Works as expected
3 - CalculateOnBarClose =true coded = Errors .. and did not 'inherit' the setting from it's caller.
(in all cases the 'calling indicator' was set to barclose=false)
This may be a NT bug.. If not, then it should be noted someplace in the help
I've attached a simple pair of indicators to show the problem.
"junk' is the primary indicator that would be added to a chart. "junk2" is the inner/called one. All it does is just return Input[0]
Junk has CalculateOnBarClose =false
Junk2 has CalculateOnBarClose =true
If you apply 'junk' to a chart, you'll see the last value is mangled.
Comment