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.
-Josh On Wed, Sep 24, 2008 at 11:10 PM, Amy <[EMAIL PROTECTED]> wrote: > --- In [email protected], "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > > > As long as ProgramModel.woCalSelectedDayData is bindable, the binding > will > > work. But you're only going to be getting a pointer to the same > object. Your > > "local" instance is the same instance as you would get with > > ProgramModel.getInstance().woCalSelectedDayData so any filters you > apply > > will also affect anything else that's bound to the same object. > > > > If you want local filtering, you will have to use a > ListCollectionView and > > bind its source to pm.woCalSelectedDayData. > > Since ArrayCollection extends ListCollectionView, what advantage to you > get from using a ListCollectionView with the same source as an > ArrayCollection vs. using a second ArrayCollection with the same source? > > > ------------------------------------ > > -- > 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]
