Interesting turn of events

[Joe Lewis Wilkins]

Well, Jaqi,

I've got egg on my face once again. Turns out that with all of the various things I have going on these days, that I must have inadvertently, trashed my final stack - the one that had all my most recent changes - the keydown events. Not finding the handlers I expected to find, I started searching the copious backups I had made and found they all lacked the final tweeks. Once rewritten, everything works fine and still opens and works under 3.5 too. It was the corresponding upgrade to 4.0 that made me suspect that it was the culprit. I'll blame it on my eyesight one more time. I REALLY have to be careful about what I trash these days, since I don't have the Finder Fonts pumped up as large as everything else with which I work.

My apologies,

Joe Wilkins

On Nov 27, 2009, at 9:21 PM, Joe Lewis Wilkins wrote:

> Hi Jaqi,
> 
> Your suggested fixes didn't fix anything. There are actually a number of other things, such as menus that don't work, though the commandkey equivalents for them do. I guess it's pretty obvious that the problem is not superficial and I'll have to spend more time exploring things than I have at my disposal. (sigh!) Actually, when I opened the stack from 3.5, I did it from the File Menu, since I've set 4.0 as the default. BTW, I am using Snow Leopard.
> 
> Thanks, once I've figured things out I'll post the cure - or what the problem is/was hopefully. 
> 
> Joe Wilkins
> 
> On Nov 27, 2009, at 7:49 PM, J. Landman Gay wrote:
> 
>> 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.
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution