Better practice to store a collection of data

[efeuvejota01]

Hello bltdavid.
I have been working with the ListSeries and they really improves the way to look at the data.

https://forum.ninjatrader.com/forum/ninjatrader-8/indicator-development/1250977-better-practice-to-store-a-collection-of-data?p=1254176#post1254176

The problems I'm facing are related with this two issues:
A) Some due to combinations of two different data, some no longer valid pivots get stocked in the trail.
Question a): Is there any chance to make some changes the code (as you kindly did with the RemoveLast) in order to have something similar to RemoveAt (used in lists)?
B) The standard and supported way to communicate between two indicators is though adding the slave indicator as private in the master indicator and then in the master indicator the plots and the variables shall be set as public ( not public static). I tried to combine both to public but the master indicator get error and doesn't save. I tried to set Values[0] to public static but l got no luck.
Question b): is there a chance to be able to set the ListSeries as public only? as i was trying, the variables (ListSeries) appeared in the intellisense, but then appear an error at the time to save the workspace.
Thank you very much!!!

[bltdavid]

I have been working with the ListSeries and they really improves the way to look at the data.

Glad you enjoy using it!

Question a): Is there any chance to make some changes the code (as you kindly did with the RemoveLast) in order to have something similar to RemoveAt (used in lists)?

Done.

I've added RemoveAt() per your request.
Download the attached file and replace your current copy.

Question b): is there a chance to be able to set the ListSeries as public only? as i was trying, the variables (ListSeries) appeared in the intellisense, but then appear an error at the time to save the workspace.

Of course.

I think the root cause is that you are unaware that all public
properties and all public variables in the Indicator class are
Xml serialized.

[EDIT: Actually, it's any class, not just Indicator. The concept
of Xml Serialization is a C#/.NET thing, not a NinjaScript thing.]

It seems that your attempt to mark a ListSeries<T> variable
as public in your Indicator is causing you problems when
saving the workspace. I'm assuming the issue is an Xml
serialization error.

How to fix it?
Simple. Same as with public properties, you must add the
[XmlIgnore()] attribute to the public variables that need
to skip Xml serialization.

For example, update this line,

public ListSeries<int> zzBars = null;

to this,

[XmlIgnore()] public ListSeries<int> zzBars = null;

I like to place the [XmlIgnore()] directly in front of the
public definition, but you could also place the attribute
on a line by itself.

-=o=-

What if you don't want to use XmlIgnore? I mean, what if
you really do need to make your ListSeres<T> persistent?
Well then, you're kinda on your own.

I've never cared about actually serializing the data contained
in a ListSeries<T>. I have always used the XmlIgnore
attribute to just ignore the variable entirely.

Remember, Xml serialization is not about sharing data
between two different running indicators. Xml serialization
is about storing instance data on disk, in an Xml file, such
that the data can be restored to a new instance later. For
ex, say you exit/restart NT, it is the saved data in the Xml
file that is used to populate the new instance after restart.

[If you really need to make your ListSeries<T> serializable,
that is an entirely different problem, and it depends on just
how complex is your type T. If I had to do it, I would use
the 'convert to a string' trick, using a special-purpose non-
browsable property, like is currently done when serializing
brushes.]

[efeuvejota01]

Thank you very much!!
Let me digest it....
FVJ