I am trying to figure out how to have a 'current' or 'active' page treatment on a given page, to show the user where they are in the site navigation. I found similar questions in this forum but no answers.
I would like to get this to work with slices / states on the master page. My workaround has been to use the master page slices / states for rollover only, and to have the 'current page' treatment on each page (overlapping the master page layer). This is inefficient because whenever changes are made to the nav, I have to change the current page treatment on every single page.
It seems to be this is what the master page should be useful for, no?
Note: I am only creating a working prototype for the client that they can view in their browser. This is not intended to create final code, I leave that to my developer. I just want everything approved by the client before the design goes to my developer, and I find that working prototypes help with this.
Thanks in advance for your kind wisdom! This is my first foray into Fireworks and so far I am finding it is way faster than Photoshop at creating mockups.
Your current workaround sounds pretty good. Unfortunately, my older version of Fireworks (FW8) doesn't have the features you're using, so it's hard for me to advise you.
Here's my suggestion: Would it help to define each nav/menu item in your master page as a symbol? You could drag a second instance onto each individual page to indicate the 'current page'—using effects or transformations to modify its appearance. Then, any changes you'd need to make later on to individual nav items could be made to the symbol, where they'd only need to be made once.
Alternatively, would it be possible to define each nav item as a button symbol (which would include multiple states)? Or to use one symbol—with multiple instances—for all the nav items?
Thanks so much for your help!
Good idea to go with a symbol. Only issue with that, is with my current nav design, when one nav item changes, it affects all the others (spacing / placement). But, still a good approach that saves time! We'll see what happens to Fireworks in CS6...