For years I've used Fireworks to create navigational element for sites. I've used it since v1.x, and knew my way around it quite well. To make a two state button, you make the off version, copy the 'frames' and change it within that second frame; slice, export, done.
FW CS4 has "states" instead of "frames". Same basic idea, one would think. No, it behaves entirely differently, causing me a long period of teeth gnashing. No local docs, only that stupid shift to on line only that takes ages to find what you need. I finally puzzle out that they've made it more like PS, where it will only behave as before if each element is on it's own layer, and that can't be the default 'background' layer it starts you on. If it is, any change to that object is changed on every "state", no matter what state is active when you change it.
Then there's Flash CS4.
I don't work much in there, usually only occasionally making slideshow type movies, where one image fades into another. Simple: load images into layers, convert to symbols, set keyframes, then on the last keyframe set alpha to 0 and so on. Right click within and create "motion tween".
First, it was difficult to find the alpha setting for the object, as they have 'workspaces' and not every one has it, apparently. Then once that's found, it's not "create motion tween" with the choice of what sort in the following dialog...it's an entirely different menu choice now.
Damn you, Adobe. Stop totally overhauling work software interfaces in the name of progress! You don't have to change it completely to justify a new license...
Just lost something like half a day to this.
Having problems, or maybe questions about WHT? Head over to the help desk!
Argh, I was thinking about upgrading my Flash as I heard CS4 supposedly incorporates some new 3D utilities which would probably make my type of animating much easier. If they messed around with too much of the UI then I'm not sure how I'd want to go...