I think we saw a problem similar to this a long time ago on this list. I don't think there was a better way than duplicating the source. However, depending on your use case you my not need to do a deep copy of the source array, so you would have multiple arrays that point to the same data so at least the data isn't duplicated in memory.
Here's the thread: http://www.mail-archive.com/flexcoders@yahoogroups.com/msg73153.html - Dan Freiman On Feb 19, 2008 3:21 PM, simonjpalmer <[EMAIL PROTECTED]> wrote: > ListCollectionView and separate filter functions > > > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, "Paul > Andrews" <[EMAIL PROTECTED]> wrote: > > > > Unsurprisingly, my Flex applications tend to have a common theme - many > > components driven from the same data, but with different filter > functions. > > > > With ArrayCollections having one filter function and needing to trigger > > Binding events, the obvious solution seems to be to duplicate the > > ArrayCollections (well duplicate the underlying array and use that > as the > > source of a new ArrayCollection) to drive different components with > > different filter functions. > > > > This seems a bit of a waste - duplicating the underlying array for each > > filter, so I wondered if anyone out there has a neat trick to avoid > this > > duplication. > > > > Paul > > > > >
