After struggling a bit to combine a TagNavigator and a few states in an application, I'm wondering - when are states preferable to a ViewStack-derived navigator? ViewStack offers several advantages:
* The MXML is clear and easy to reorganize. * You can get a least some kind of help from the visual designer in Flex. (I like to use it for previews and to get my interface objects into rough order.) * It seems to work flawlessly. States, on the other hand, end up adding a ton of rendering instructions to the MXML. It's pretty awkward to work with the objects either in the MXML or the designer view. >From reading various docs and blobs I've gotten the impression that states are considered superior for some reason. I just can't tell what that reason might be. A clear advantage I can see to states is when the bulk of the objects are shared between the two states - then it's simpler to have one instance of those objects. I'd be really curious to hear what more experience people think about this. (I still feel like I'm floundering around in Flex a good deal of the time.) Thanks!
