Hi all, I'm new here...and still very wet behind the ears...but I'd probably do a viewstack and put my own buttons up for navigation. That way you can switch panes however you like. I'm doing something similar right now for one of my projects.
Hope to meet many of you at Max...I'm the bald guy, I'm sure I'll be the only one. :-) -John On Mon, 18 Sep 2006 7:23 pm, Tim Hoff wrote: > It's only bad design if it doesn't solve the individual use case. > It's possible that Javier wants the same functionality as a self- > guilded checkout, that uses an accordion control, but only allows > the user to proceed to the next step after the current step has been > successfully completed. If that's the case Deepa, your earlier > solution would fit the bill. > > -TH > > --- In [email protected], "Deepa Subramaniam" > <[EMAIL PROTECTED]> wrote: >> >> Yes, I agree, its bad design. The benefits of exposing tabs for > browsing >> and then disabling them and forcing the user to follow some other > route >> to navigate through the container makes no sense to me but I was > just >> answering the poster's initial question :-) >> >> >> >> ________________________________ >> >> From: [email protected] > [mailto:[EMAIL PROTECTED] On >> Behalf Of Paul Andrews >> Sent: Monday, September 18, 2006 12:45 PM >> To: [email protected] >> Subject: Re: [flexcoders] How can I block a TabNavigator ? >> >> >> >> ----- Original Message ----- >> From: "Deepa Subramaniam" <[EMAIL PROTECTED] >> <mailto:dsubrama%40adobe.com> > >> To: <[email protected] <mailto:flexcoders% > 40yahoogroups.com> > >> Sent: Monday, September 18, 2006 6:52 PM >> Subject: RE: [flexcoders] How can I block a TabNavigator ? >> >> > What you can do is iterate through the TabNavigator's tabs and > disable >> > each of them. By disabling them, the change event will not get >> emitted. >> > Use TabNavigator.getTabAt() and set the enabled property to > false for >> > each Tab. >> > >> > Now, when you disable a Tab, the Tab will assume the look of its >> > disabled state (grayed out, etc). You probably want the Tab to > look >> > enabled even if it is disabled - in which case you'll have to > change >> the >> > Tab's disabledSkin. >> > >> > HTH - >> > deepa >> >> Horrors. It's really good making the user think (s)he can navigate > the >> tabs, >> then discover they can't. Is this really good practice? >> Even with the disabled tabs - hey I completed the info, now it's > become >> invalid.. >> >> Paul >> > > -John Nagle -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
