This content has been marked as final. Show 3 replies
Well, it does make sense to me. The effect runs when you delete or add an item in the data provider. It's not meant for filtering effects, because really the data have not been changed or deleted, its just being viewed differently (some items are hidden).
Having said that, why don't you cook up an effect sequence for what you want to see happen, and then play when the filter function runs? You could fade out, then fade back in, etc. Should be pretty straightforward.
Thanks for the explanation, never looked at it that way. Makes sense.
So, you mean when I assign the filterFunction, I then would call my sequence.play ? Sorry, not sure how that would work.. would you happen to have an example please?
Since calling refresh on a dataprovider would trigger a "ListChange" event, you could listen for that, like:
Assuming you're doing a fade out/fade in effect, create those separately, then work them into the flow of events where needed. The targets property of each effect can decide what to fade in/out.
I've never tried this. I'd assume that the COLLECTION_CHANGE event is called AFTER the List is refreshed, so timing an effect could be an issue unless you fadeOut.play()---> effectEnd event--> call refresh method on dataProvider--> COLLECTION_CHANGE event--> listChangeHandler called--> fadeIn.play()