Indicator Not Showing Up in Selection Panel on Chart

[Jim-Boulder]

I suddenly am having an issue where I copy an existing indicator that is working ( and shows up in selection list) - where the new copy is saved in its own unique name by changing the name of the code and in the Name = statement below.

Also it compiles fine, and shows up as the new code name in the "Indicator list" within the Ninja Editor...

Any clues why this is happening?

Code is attached....

The Name statement:

if(State == State.SetDefaults)
{
Calculate = Calculate.OnBarClose;
Name = "CWH Data Study";
path = NinjaTrader.Core.Globals.UserDataDir + this.Instrument.FullName + "-CWH Study Data.txt"; // Define the Path to our test file
}

[NinjaTrader_ChelseaB]

Hello Jim-Boulder,

I think i'm not understanding correctly.

You have created a copy of a script using a new name, and the new script has the new name, is this correct?

That would be the expected behavior..

Are you saying that the new script has the old name?

[Jim-Boulder]

Sorry for the confusion.

I have an existing script "A" which is working fine. I do the following:

1) I make a copy of the script in the Ninjascript Editor
2) I change the Name = "A" to :B:
3) and do a save as "B",
4) and then compile "B" with no errors.

Both "B" and "A" show up in the list of indicators in the Ninja Editor, but when I go to a chart and try to add "B" it is NOT showing up in the list of available indicators in the chart dialogue list, however "A" is showing as available.

[Jim-Boulder]

Found the Issue

I found the issue - even though the script compiled without error, there was an error in the code that apparently only triggered when applying to a specific instrument.

I resolved the issue (I was not checking for a null instrument name before using it in the file path string) - and now it appears on the available indicator list in the chart dialog box.

Thank you.

[NinjaTrader_ChelseaB]

Hi Jim-Boulder,

Thank you for letting me know you've resolved the behavior...

However, I'm curious if the code in strategy B is exactly the same as strategy A with a different name, how is strategy A not also affected by this error?