Property Grids - Expandable Objects & BarsPeriod

[reach4thelasers]

Hey there,

I have a couple of questions about Property lists I hope someone can help with.

Firstly, I'm using the ExpandableObjectConverter TypeConverter to display my properties; however when the properties dialog first opens all of my settings are collapsed. I can't figure out how to make it open fully expanded; is there a way to achieve this?

Secondly, while investigating how to expand the property grid by default. I looked at this indicator:

http://ninjatrader.com/support/forum/showthread.php?t=97919

It doesn't do what I need, but it presents the BarsPeriod on the property grid which is useful for setting up multi-timeframe indicators. I can't figure out how this is being done; the sample code makes no reference of a BarsPeriod. And if I reference a BarsPeriod object directly, I get loads of properties I don't require.

[NinjaTrader_Jesse]

Hello,

Thank you for the post.

Regarding expanding the properties automatically, I am unaware on anyway to do this for expandable objects. I will put in a question to development to see if there are any ways for attributes or another syntax to expand them.

For the BarsPeriod selector, you could use the following code. It appears the image you provided is no longer the same as the file that was linked. It may have been updated at some point after you downloaded it is why you cannot find that property:

[NinjaScriptProperty]
[TypeConverter(typeof(BarsPeriodConverter))]
[Display(Name="Select BarsPeriod", GroupName = "Parameters", Order = 0)]
public BarsPeriod BarsPeriodInput
{ get; set; }

For this to appear, you would need to first assign a value because this can be null:

if (State == State.SetDefaults)
{
	BarsPeriodInput = new BarsPeriod();

i look forward to being of further assistance.

[Harry]

Expandable property reverting back to default values after recompiling

Attached is a sample for defining exandable properties via a custom class.

Basically it works well as it will correctly serialize the public properties of the custom class such that they can be saved being part of a chart template or workspace.

The only problem here is that the porperties of the custom class will revert bac to default values on an open chart, when NinjaTrader recompiles.

We had this same issue with enums (see #ID 11504), which was then fixed with the release NT 8.0.7.0.

How would I avoid that the properties revert back to the default values after a recompile?

[reach4thelasers]

I get around this by setting the persisted property with the ReadOnly attribute rather than Browsable(false) this unfortunately displays the serialized string in the property grid, but gets around the problem of settings reverting on rebuild.

Details here:

http://ninjatrader.com/support/forum/showpost.php?p=509406&postcount=6

[Harry]

Any idea why the parameters of a subclass revert back to default parameters when NinjaTrader compiles?

I have also looked at the sample provided by JessicaP here, and it does not work either.

http://ninjatrader.com/support/forum/showpost.php?p=511115&postcount=12

I have used this approach in a number of indicators and they currently do not keep their indicator settings, when NinjaTrader compiles.

[eDanny]

NT7 was the same way.

[Harry]

NT7 was the same way.

Did you find a solution to the problem?

[eDanny]

Unfortunately not.

[deltaZ]

I've run into this same problem. I can also confirm that the NT-provided expanded class example has this issue as well. The values revert to default on recompile.

Anyone able to shed new light on this issue?

[Harry]

There has been no progress with this issue. There is another thread were we had discussed it, but the sample provided so far do not work.

Maybe you could support me in obtaining a solution for this case.

https://ninjatrader.com/support/forum/showthread.php?p=525743#post525743

[wbennettjr]

This is an old post but if you are still having issues with the values reverting on compile, I believe I can post a sample of how to fix it. I am currently working through some issues with this and restoring from serialized versions but I believe I have enough to point you in the right direction. The code may be a bit more clunky than it needs to be since, as I stated, I'm still working through it.

If you do want a sample, provide the exact details of what you are trying to achieve. I'm building a more general structure so I may need to tailor to suit your needs.

Wil