Indicator not properly restored when new enum value added to enum input

[aslane]

If I have an indicator that uses an enum as an input, and then add a new enum value, any instances of that indicator do not retain the values for said input, and instead reset to the default value.

First is this a known issue?

Second, seeing as this is just an int value, can this be serialized in/out as an int value vs an enum?

[aslane]

I tried serializing similar to a brush, by converting enum to int to string and back again, but this did not solve the issue.

[NinjaTrader_Jesse]

Hello aslane,

Thank you for the post.

I tried a quick test using an indicator template but was unable to see the problem. Can you provide the specific steps you are using along with an example of how you defined the enum in your script/where it was defined in the script?.

Also what changes are you making to the enum, are you adding a new value to the end of the enum or somewhere in the middle to where it would change the order?


I look forward to being of further assistance.

[aslane]

Attached is a simple dummy example with a single input that shows the issue.

The enum is declared in the global namespace. Each enum entry has a specific value defined, including an ending value that will always be at the end.

Once placed on a chart, change the AvgType input to EMA (which is not the default value set in SetDefaults). You can save workspace at this point.

Now, the following causes the issue:

1. Add new enum value (I have one commented that can be added)
2. Compile the ind
3. Go to chart and hit F5 to reload NS

At this point the input is reset to the default value instead of maintaining its current value.

If you now close the workspace without saving and then reload workspace that was previously saved, it will have the correct value restored.

EnumIssue.cs

[NinjaTrader_Jesse]

Hello aslane,

Thank you for providing the sample.

I was able to see the change with this sample, I will need to research this further to see if this would be expected or something I can report. Once I have more details I will provide an update here.

I look forward to being of further assistance.

[aslane]

One item I forgot to mention is that it does not matter if the input is a NinjaScriptProperty or not.

[aslane]

Any update?

[NinjaTrader_Jesse]

Hello aslane,

Not at this time, if I have anything additional that I can provide I will update the thread.

I look forward to being of further assistance.

[NinjaTrader_Jesse]

Hello,

I just wanted to provide an update, this item has been logged with development and can be tracked using the ID: NTEIGHT-14346.

I look forward to being of further assistance.