Thanks. I also have a couple of cases involving stacked column series, where I wonder if I should build a custom implementation of IList or ICollectionView.
eg. the raw data has an integer (representing an enum). There is a column series for each enum value. I can either use the filter technique to make a data provider corresponding to each value of the enum. Or I can have a single custom collection which returns an object with a property for each value of the enum, and use yField. Any experience reports on the relative efficiency of these two approaches would be much appreciated. I find myself wishing collections supported a mapper function in addition to a filter function. On Wed, Apr 16, 2008 at 10:42 AM, Daniel Gold <[EMAIL PROTECTED]> wrote: > > > > > > > I've used that approach many times. Store the data in a central model, views > each have a local ArrayCollection with a filterFunction and the source set > to the data in the model. > > > > On Wed, Apr 16, 2008 at 12:37 PM, Richard Rodseth <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > > > > Hi > > > > I'm working on a dashboard where several charts share common data. I > > was thinking that each chart series could have a data provider which > > is a collection with a filter function, and I could set the source > > array of these collections to the same array. Sound reasonable? > > > > Thanks > > > >
