Is there some reason that you cannot use the *change *on the viewStack
itself?  There are also *show*/*hide *events on the underlying containers.
I perhaps mistakenly assume you have tied this to a tabNav or similar
navigation container.

On Wed, Jul 30, 2008 at 8:56 AM, Cameron Childress <[EMAIL PROTECTED]>wrote:

> What's the best event to listen for when a *specific* child of a
> ViewStack becomes active?  I'd like to set some defaults on a specific
> child each time it becomes active (not just the first time, and not
> just when it is created) and can't seem to find the right combination.
>  I'm using a fairly common pattern to change the viewstack...
>
> private function getView(i:int): Container {
>       if (i == VIEW_MAIN) {
>               // can't fire event here, main doesn't exist yet!
>               return main;
>       } else {
>               return login;
>       }
> }
>
> <mx:ViewStack selectedChild="{ getView( viewState ) }" >
>       <view:Login     id="login" mysteryEventToListenFor="???"/>
>       <view:Main      id="main" />
> </mx/ViewStack>
>
> Advice would be appreciated...
>
> Thanks!
>
> -Cameron
>
> --
> Cameron Childress
> Sumo Consulting Inc
> http://www.sumoc.com
> ---
> cell: 678.637.5072
> aim: cameroncf
> email: [EMAIL PROTECTED]
>
>
> -------------------------------------------------------------
> To unsubscribe from this list, simply email the list with unsubscribe in
> the subject line
>
> For more info, see http://www.affug.com
> Archive @ http://www.mail-archive.com/discussion%40affug.com/
> List hosted by http://www.fusionlink.com
> -------------------------------------------------------------
>
>
>


-- 
Scott Talsma
CTO, echoEleven



-------------------------------------------------------------
To unsubscribe from this list, simply email the list with unsubscribe in the 
subject line

For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------

Reply via email to