subscribe to the TabNavigators click event. From here, execute a
validation routine based on the last known tab clicked (ie default
is tab0, then if user clicks tab1, then update a var to indicate
such).
Validate that tab, if it fails, then simply fire an exception routine
(ie popup) and
] On
Behalf Of Scott Barnes
Sent: 21. kesäkuuta 2005 10:11
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] TabNavigator gimmick
subscribe to the TabNavigators click event. From here, execute a
validation routine based on the last known tab clicked (ie default
is tab0, then if user clicks
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] TabNavigator gimmick
Thanks Scott, but the problem is : Unknown attribute 'click' on
mx.containers.TabNavigator.
So there is no click event on TabNavigator, I tried placing it on
change-event but it does not affect it if set selectedIndex=x
http://www.macromedia.com/go/wish
Tracy
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Doodi,
Hari - BLS CTR
Sent: Tuesday, June 21, 2005 10:17 AM
To: 'flexcoders@yahoogroups.com'
Subject: RE: [flexcoders] TabNavigator gimmick
Hi All
Hi.
I was just trying to do this a week ago and worked with
Macromedia gold support. This turns out to be rather difficult to do,
partially because the tabnavigator is actually a tabBar attached to a
viewstack. I had code that would fire on the tabnavigator's change event
to determine if
'
Subject: RE: [flexcoders]
TabNavigator gimmick
Hi All,
I have same
situations and unable to resolve.
Can we request
macromedia development/research group to provide a
new event called changing to
TabNavigator controls which should fire
before change event and provide
mechanism either go ahead
6 matches
Mail list logo