Hi Joel, I took a look at the code. It looks like it would work. I'm wondering if you considered: 1) directly accessing the underlying array instead of using super methods 2) storing the unfiltered data as an Array instead of an ArrayList.
Thoughts? -Alex On 1/3/17, 3:28 PM, "JoelProminic" <j...@prominic.net> wrote: >I updated the JIRA issue >(https://issues.apache.org/jira/browse/FLEX-35232) >with a modified version of the project where the visible elements of the >FilteredArrayList are stored with the superclass logic, while the full >list >is maintained as a separate ArrayList instance. This makes >FilteredArrayList throw the appropriate itemAdded, itemRemoved, and >itemUpdated events for the visible list (itself) rather than for the full >list, as it did in the previous version. > >The updated example also automatically refreshes the list when you click >the >Update/Add/Remove Entry buttons, for convenience. > >Otherwise, the logic has the same limitations discussed above. > >Joel Anderson >My Apache Flex community contribution is working on the open source >Moonshine-IDE.com for FlexJS. > > > > >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/Filter-function-to-Ar >rayList-tp57239p57871.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
