Roonius RValue Indicator ninja 7

[MicroAl]

I tried to compile the RValue charts indicator in Ninja 7 it is having trouble with the following two lines

outlineColor = ChartControl.BarOutlinePen.Color;
outlineWidth = ChartControl.BarOutlinePen.Width;


I can see that there is no property now for BarOutlinePen
is there an equivalent in Ninja 7?

[NinjaTrader_Dierk]

I suggest contacting the author (roonius?). I believe we discussed that issue with him before.

[r2kTrader]

I tried to compile the RValue charts indicator in Ninja 7 it is having trouble with the following two lines

outlineColor = ChartControl.BarOutlinePen.Color;
outlineWidth = ChartControl.BarOutlinePen.Width;


I can see that there is no property now for BarOutlinePen
is there an equivalent in Ninja 7?

I'm getting an issue that might have something to do with this as well. It only took me two days to track this down, but I am better debugger as a result ;-)

Ok, in my indicator (which works find in 6.5) this line is causing an error (which I have posted below)

LINE:
if (ChartControl.ChartStyleType == ChartStyleType.CandleStick)

The indicator compiles and it works fine when I put on a chart, but when I call within my strategy, it blows up my strategy with this error.

ERROR:
Error on calling 'OnBarUpdate' method for indicator 'TrendIndicator1' on bar 2: Object reference not set to an instance of an object.

-----UPDATE----
Actually, as I think about this, I should also add that I am overloading the indicator with another bars series, "BarsIndex[1]" and I think what is happening is that that Bars/Period or whatever does not have a ChartControl bound or associated with it?? (I could use a bump here, not looking for help debugging as I found the problem, just want to confirm is this is a bug or not)

Am I close?

I'm sure I can get around this by testing for null value, but I am curious to know about this as it will seemingly have a grand effect on a great number of indicators which are used in Strategies and overloaded to a different barsarray or whatever. (Multiperiod based Strategies).

I have confirmed my findings. This patch resolved the issue.

(ChartControl !=null && ChartControl.ChartStyleType == ChartStyleType.CandleStick))

So, and this was probably documented and I missed it, but here are some questions.

1. When you are writing a strategy that has more than one bars object, and you use that bars object (secondary or greater, non-primary) to overload an indicator that you add e.g. SMA(BarsIndex[1], 20), the indicator object will NOT have a chart control?

2. Is this specific to 7, or was this always the case even in 6.5


Thank you, I hope this helps someone else because it took me a while to crack the case on this one.

[NinjaTrader_JoshP]

ChartControl is undocumented and as such is unsupported. The behavior you are seeing could be the case, but since it is undocumented is subject to change if deemed necessary by NT internals. Unfortunately I would not know if 6.5 is different or not.

[r2kTrader]

ChartControl is undocumented and as such is unsupported. The behavior you are seeing could be the case, but since it is undocumented is subject to change if deemed necessary by NT internals. Unfortunately I would not know if 6.5 is different or not.

Josh,

I don't think it would hurt to document my findings. Many indicators use ChartControl and I see no reason not to bring it to people's attention.

Your call. I did the homework, it will only help others.

[NinjaTrader_Dierk]

This goes back to conversations we had with you in the past: there are clear limitations to what is part of NinjaScript and what is not. Our position has not changed.

[Mindset]

r2ktrader

I am with you on this one.
My coding skills are still fairly limited but the lack of support for ChartControl is just frustrating and limiting.
I used to use ChartControl.PlotExecutions to turn execution display on and off but that has disappeared and of course you can't get any help to find out how to do it from NT.
This was a very helpful post r2k. I had got my code working but the log was full of object references not set to instance errors.
Your snippet solved the issue - so, NT you really ought to support ChartControl IMHO.

[eDanny]

ChartControl is undocumented and as such is unsupported. The behavior you are seeing could be the case, but since it is undocumented is subject to change if deemed necessary by NT internals.

I have seen this answer with so many questions about programming and half heartedly agreed but I just got a flash. Why are these features any different than NinjaScript that is subject to change if deemed necessary by NT internals?

[NinjaTrader_JoshP]

eDanny,

NinjaScript documented methods and properties are preserved for backward compatibility as much as possible. NT internals are subject to change without notice. The line is drawn on documented methods and properties. Thank you for understanding.

[eDanny]

I understand Josh but what determines whether properties and methods are documented or not documented? If people are using certain undocumented features could you add them to documented NinjaScript?

[NinjaTrader_JoshP]

eDanny,

What determines what is documented is by what we have internally outlined as what we can and cannot offer reasonable support on. The use of internal properties has a lot of implications that we just can't present cleanly and thus have drawn the line to not support it. Unfortunately this is a reality of the situation in that we have to be able to clearly define the box in which we can offer support on or else we would be completely swamped with technical C# questions that will quickly exceed all of our support resources. We do understand at times people may want to use some undocumented features which is fine, but it will have to be used as their own endeavor. After all, it is through this model that we are able to provide such cost effective support which ultimately translates to lower costs to the users of NinjaTrader in terms of license fees.

Thank you for understanding and merry Christmas.

[eDanny]

Merry Christmas to you.