How to make collection editor appearing in the property grid

[rfsettling]

Hello,

I have indicator ported from NT7 to NT8 which uses array of objects.
I does not work NT8. Array is showing but there is no edit button to add or remove elements

Here's the simple example

public class MyCustomIndicator : Indicator
{
        [TypeConverter(typeof (ExpandableObjectConverter))]
        public class TimeRange
        {
            public TimeSpan Begin { get; set; }
            public TimeSpan End { get; set; }
        }

        //How to edit this collection in property grid?
        public TimeRange[] TimeRanges { get; set; }

[NinjaTrader_AlanP]

Hello rfsettling,

This would not be possible and require having two separate controls.

I have attached a sample demonstrating this.

Please let us know if you need further assistance.

[rfsettling]

Example you've attached shows me two properties of TimeRange type.It is absolutely is not what I'm waiting for. I need dynamic collection of TimeRange without any restrictions by it's length.

It's a trivial task for standard PropertyGrid. And it worked perfectly on NT7 with Windows Forms property grid. But now, with this new WPF grid, it doesn't. There must be some editor for this purpose

[NinjaTrader_AlanP]

Hello rfsettling,

I have attached a sample which allows you to click the cell for time range under indicator properties and edit its time range.

Please let us know if you need further assistance.

[rfsettling]

This is exactly what I need.
Thank you

[koganam]

Hello rfsettling,

I have attached a sample which allows you to click the cell for time range under indicator properties and edit its time range.

Please let us know if you need further assistance.

I have noticed a whole bunch of PropertyEditors being used in code examples from NT Support reps on the forum, but none of them seem to be documented.

Can we get documentation added for all the property editors and examples of how to use them?

[NinjaTrader_AlanP]

Hello Koganam,

Good suggestion, I will put in a feature request and pass the suggestion on to development that documentation be added to the helpguide covering PropertyEditors.

This feature request is being tracked under SFT-2286.

Thank you for your suggestion

[koganam]

Hello Koganam,

Good suggestion, I will put in a feature request and pass the suggestion on to development that documentation be added to the helpguide covering PropertyEditors.

This feature request is being tracked under SFT-2286.

Thank you for your suggestion

Has there been any progress on this?

Thanks.

[NinjaTrader_AlanP]

Hello koganam,

Regarding SFT-2286, it looks like its still being considered. If another user wanted to add a vote to this SFT, I can add a note to the request.

Please let us know if you need further assistance.

[Zeos6]

Hi AlanP,

I agree with koganam. Would be a very useful feature. Please add my vote. Thank you.

[NinjaTrader_AlanP]

Hello Zeos6,

Thank you, I will submit a vote for you as well as myself for this feature request.

[rfsettling]

I vote for this

[koganam]

Hello Zeos6,

Thank you, I will submit a vote for you as well as myself for this feature request.

2+ years gone. Are we still waiting for this?

[NinjaTrader_ChelseaB]

Hello koganam,

Thanks for checking into SFT-2286.

This has not been implemented at this time.

Not all requests will be implemented and this is largely driven by demand.

Please note, it is up to the NinjaTrader Development to decide if or when any request will be implemented.

[koganam]

Hello koganam,

Thanks for checking into SFT-2286.

This has not been implemented at this time.

Not all requests will be implemented and this is largely driven by demand.

Please note, it is up to the NinjaTrader Development to decide if or when any request will be implemented.

This is a documentation request, not a development request. Instead of getting piecemeal information of what ALREADY exists, just tell us what is already there. Yes, it takes time, Still, it is just giving out information that already exists, not creating new code. So, yes, I understand that: "Not all requests will be implemented ...". However, there is nothing to implement. Just provide information that already exists, and that NT support is already dripping and doling out like expensive diamonds. I apologize for my sarcasm, but it is warranted in this case.