What Goves?

[Bill Lynn]

> well if the key commands are your only problems, that's not
> too bad..

Not too bad! It's a major flaw in my estimation. And since others have 
reported it I think it warrants investigation. It's extremely tedious 
having to use the mouse and menus to accomplish repetitive tasks and it 
slows things down tremendously. By the way, reseting preferences to 
their defaults didn't help.

> even though your license runs out, your copy of RunRev will
> still be a good full-working copy after that date

I understand that. My point is that I'm not inclined to renew the 
license for software that has these problems.

> Does it also happen when you create a brand new stack? If not, then the
> problem may be a commandkey handler in your older stack.

I'm describing problems in a brand new stack.  I'm not using any 
command key handlers. I've also checked and rechecked to make sure that 
messages are not suppressed. The strange thing about command key 
equivalents is that when I try using them, the corresponding menu will 
flash but the operation will fail. I'm completely baffled by this.

This is a major disappointment for me. I've just wasted the past seven 
months banging my head against a wall with Director MX trying to 
understand why a company like Macromedia refuses to accept the fact 
that transition effects are important enough to fix. Can you believe 
it? Transitions in OS X projectors are broken. They just plain don't 
work. So for the past seven months I've been unable to ship products 
using Director MX.

As I continue to work with Rev 2.0.1 I'm discovering other quirks. For 
example, when I transition to a card that contains a default button the 
button magically appears on the starting card before the transition 
begins.

I understand that the the Rev people are at MacWorld Expo. Is anyone 
from the company monitoring this list this week and can you address my 
concerns?