as being useful when you want to replace a whole section. Look at view
1. Now look at view 2. States are better for modes of a component, now
we're in expanded view, now we're in thumbnail view. As soon as you
want the same component moving around I think you'll use a state. In
some cases I might have a state for the larger component where one of
the things I'll change in the state is the selectedIndex of a ViewStack
:-)
I think it's going to take the community some time to use the features
before coming up with a best practice pattern of where you would use one
over the other.
Matt
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Rick Schmitty
Sent: Tuesday, May 02, 2006 8:49 AM
To: [email protected]
Subject: [flexcoders] mx:states vs mx:viewstack when and which?
Hello, I've seen some examples with Cairngorm using either states or a
viewstack to display the current screen. I was wondering what were
the advantages/disadvantages and when you should use one over the
other? Seems like both can have the current view bound to a selection
thanks
--
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
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

