Well if you're using b = new ListCollectionView(a), you can replace a.source and your results at b will upate. Not so if b = new ArrayCollection(a.source);
And you don't need the extra functionality of ArrayCollection, which is basically an amalgamaion of LCV (for insert, filtering, removal support, etc) and ArrayList (used as the source for the LCV). -Josh On Thu, Sep 25, 2008 at 5:28 AM, Amy <[EMAIL PROTECTED]> wrote: > --- In [email protected], "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > > > Because if you have collection A, and components bind to it, all 3 > > components will see changes caused by the filter. But if you create a > new > > ListCollectionView (we'll call it B) and point it to A, you can put > filters > > on B without affecting A. > > How is that different from creating a new ArrayCollection B and binding > to that? > > -Amy > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Alternative FAQ location: > https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
