Joe Lewis Wilkins wrote:
Hi run-revers,
After licensing 4.0 I opened a stack that I had completed using 3.5.
There are a number of things it no longer does correctly, associated
mostly with keydown events. So I tried to open it directly from 3.5
after closing it under 4.0. It then reported that the stack is
corrupted. After closing 3.5 and double clicking directly on the
stack, it once again opened, and the commands/events that weren't
working before are still not working. So, it seems that opening a
stack with 4.0 makes it so you cannot go back and use it with 3.5.
Kind of nasty turn of events.
I haven't seen any differences between keydown/keyup events between
versions. The most likely reason for loss of key events is that a
handler is intercepting them somewhere. Try suspending development tools
and see if they work again. Also make sure the Messages button is not
bolded in Rev's toolbar; turning off messages will stop many events from
being passed to your stack.
The issue with 3.5 reporting a corrupted stack was a known bug, now
fixed in 4.0. Your stack was never corrupted, it was just a glitch which
you could work around by opening the stack from the File menu rather
than by double-clicking. The bug occured even before 4.0 was available,
and the same warning appeared with 3.5 stacks. It was spurious and did
not affect or alter the stack in any way. The bug only occured on Snow
Leopard machines.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
