Yes, I frequently listen for updateComplete event to hide a spinner showing
busy states, especially if the lists are long and use complex item renderers,
anything that makes them slow to update onscreen. It's reliable if (and only
if) you have records in the underlying dataProvider. I found through trial and
error though, that if the dataProvider list is empty, then updateComplete
doesn't get fired. Again, for initial loading of lists, or if you are updating
the underlying collection in a way that will cause the list to update.
For example:
<s:DataGroup width="100%" dataProvider="{_dataProvider}"
contentBackgroundAlpha="0"
itemRenderer="{itemRenderer}" updateComplete="Alert.hideBusy()">
Cheers,
Erik
On Jan 9, 2018, at 2:23 PM, bilbosax <waspenc...@comcast.net> wrote:
I don't know if this how anybody else would do it, but it seems to be working
at this point. I have a list in the state that I am moving to from the
state that contains the map. I listen to the updateComplete event on the
list, and when that fires, I dispatch an event that hides the map. This has
the effect of making it look like the map and the new state change at the
same time, which is what I wanted. Even though this is working, I am
curious if there is a more standard event that most people would react to.
Let me know if you have any thoughts.
--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/
