NinjaScript Editor Bug

[Skechers]

Hello,

There is an strategy that has a field label that is persistent. I have removed the label from the ninjascript editor, added back with a new label name. Compiled. The label does not change.

I've deleted the strategy, created a blank strategy with the same name and copy pasted the source. It shows up with the old label name, even though the properties show the new name.

I have deleted custom.dll and the copy of that dll. Recompiled. Same old label.

If I save as a new strategy with a different strategy name, the new label is shown.

This is really annoying.

Many Thanks, Caesar.

[NinjaTrader_Jesse]

Hello Skechers,

Are you referring to the Name = "" inside the strategy?

If you make changes to scripts OnStateChange or their public properties you need to re apply the script after recompiling. If you just do a F5 reload or re enable a strategy it wont have the code changes.

[Skechers]

No, it was the AddPlot name. I can't reproduce it now ... oh well.

[Skechers]

Hello Jesse,

It's definitely a bug. I can repro it by creating a new strategy with a new different name, copy and paste from the one with the bug.

I delete the one with the bug, and compile the new strategy. The AddPlot rename works.

If I save the strategy with the same name that had the bug, the bug reoccurs.

There is a cache somewhere that needs to be deleted.

I haven't reinstalled from scratch and restoring the strategy.

I have reinstalled and it looks like the bug is not reproducing so far.

Many Thanks, Caesar.

[NinjaTrader_Jesse]

Hello Skechers,

Unfortunately the details provided don't help to understand the problem or what you were seeing happen.

If you are making changes to AddPlot compiling is one step of the process to see that change, to visibly see that change in the user interface you need to remove and re apply the script. If you are doing a F5 reload then it won't update by doing that. Changing default properties or items like plot names/public properties are not reflected for F5 reloads.

If you otherwise are doing something which is having an unexpected outcome we would need the exact details of what steps you followed and what code was used. We otherwise won't be able to explain what is happening without knowing all of the details surrounding the use case.