How to create non-selectable readonly property grid element?

[fx.practic]

Hello.

I need readonly parameter for strategy.

I did it in this way:

[ReadOnly(true)] 
[Range(1, int.MaxValue), NinjaScriptProperty]
[GroupName = "Periods", Order = 1)]    
public  int Period1     { get; set; } 

It works correct in StartegyAnalyzer but, property still changeable when Strategies dialogue when applying strategy on chart.

How to make property unchangeable (but visible) everywhere?

[NinjaTrader_Jim]

Hello fx.practic,

Thanks for your post.

I would not expect the property grid behavior to be different for strategies applied to a chart vs. indicators. I am also seeing that indicators can use the ReadOnly attribute without issue in a chart, but we see the difference in behavior with strategies.

I'm looking into this further and will keep this thread informed as this develops.

In the meantime, I would recommend making a property private if you do not want it to be modifiable.

Thanks for your patience while we look into the ReadOnly attribute further.

[fx.practic]

Ok, thank You. Will be waiting and monitoring this thread.

[koganam]

Hello.

I need readonly parameter for strategy.

I did it in this way:

[ReadOnly(true)] 
[Range(1, int.MaxValue), NinjaScriptProperty]
[GroupName = "Periods", Order = 1)]    
public  int Period1     { get; set; } 

It works correct in StartegyAnalyzer but, property still changeable when Strategies dialogue when applying strategy on chart.

How to make property unchangeable (but visible) everywhere?

Remove the setter from the property definition?

[NinjaTrader_Jim]

Thanks for the hint koganam.

To touch on this more, the setter for the property does appear to be disabled, and the property is "read only" when the attribute is used directly, but the property's control is still "modifiable" even though the value gets reverted. This could be permissible to some, but this shows a bigger issue when using a TypeConverter to modify the property grid behavior as we seen in the example here.

The setter cannot simply be removed without more modifications, but you could use a backing field property (like we see in NinjaTrader 7 properties) to achieve read only behavior. However, this would ultimately still provide the same behavior witnessed at the current moment.

I've reported the matter internally, and I'll update this thread with more details as they come.

[fx.practic]

koganam, thank You for idea.

If just to remove setter - code not compiled.

I made parameters in .Net 3.5 style.
They looks in another way, but values unchangeable as I need.

[fx.practic]

Thank You, Jim.

[koganam]

koganam, thank You for idea.

If just to remove setter - code not compiled.

I made parameters in .Net 3.5 style.
They looks in another way, but values unchangeable as I need.

Hm. Strange. As that is the documented Microsoft method.

ref: https://docs.microsoft.com/en-us/dot...ted-properties.

But yes, using regular properties is a very viable way to do things.

[NinjaTrader_Jim]

Hello fx.practic,

The issue reported has been confirmed as a bug and has been given the ticket ID NTEIGHT-12976. The number for this ID will be noted in the Release Notes page of the help guide when a new version of NinjaTrader gets released including a fix for this issue.

Release Notes - https://ninjatrader.com/support/help...ease_notes.htm

Please let us know if we can be of further assistance.