I can't see your attachment. You may need to rename the FXP to something more innocuous-seeming, like TXT (stupid forum software, I know)...
One thing you might try is to explicitly toggle on and off the "selected" property in state1. Let me know if this works and I'll send the long explanation of why it works...
Adam, that totally worked. I tried for hours to get it working. Thanks, Don/monkamoo.com
So, here's the medium-long explanation of why that works...
When you're working with states, there's a difference between properties/settings you've never touched before vs. ones that you've done some editing on. If you've never touched a property in a given state, it's essentially "open" or "free." If the SWF's user takes actions (such as typing in a text box or clicking a toggle button) that change the component, switching states to another state where that property on the component is untouhed or "open" will leave it as-is -- that is, as the user left it. This is useful behavior in many cases (e.g., "Search" text field in the Results state should still show the text the user entered in the StartSearch state).
But once you've edited a property, even if you eventually edit it back to its original value, it's now "explicitly set." This means that when you transition into the state where you did the editing, we blow away whatever value the setting had in the state you just left -- even if it got that way due to user input -- in order to make the setting match what you explicitly set it to.
Hope that makes a little more sense. We are definitely looking carefully at ways we can expose this distinction better within Catalyst.
Long explanation is on its way...give me a few days...
Beautiful. Thanks, Peter!