1 person found this helpful
That's interesting! I'm no expert on this, but I suspect that in the world of Fireworks, animations and buttons (the two uses of States) are mutually exclusive. They're not meant to be combined.
May I ask why you're creating a second state for your page? Would it work to define it as a new page instead?
thanks for your time!
Well I'm not sure if i have a good grasp of the concept of pages and states.
What I wanted to do was this:
I created a Master page with a header and a menu.
The menu has buttons with defined up/over states.
Now since this is on a master page, the header is shared to all subsequent pages.
I created sub pages sharing the master page header with differing content.
Now what I wanted to do was to display certain changes to subpages so that my
customer could evaluate different approaches. Varying color
layouts for example. And I thought the best way to do so was to simply
copy the state and change the affected areas.
But then the master-menu is just not right (all buttons on "over"-state...)
So not sure if thats how I'm supposed to do it. But since it doesn't work, probably not.
I think the quickest solution is to just stick to pages. But then I ask: What are states for anyway?
I just read through your links and i think i found kind of a workaround:
Just dont use the "master page" functionality, but the "share to all pages" option instead.
That way the menu wont change up/over on multiple states.
Ah, so you're using States to create Layer Comps (à la Photoshop)! That makes sense.
I'm glad you found a workaround.