Hello,
I've found a bug, that I found hard to reproduce at first, but it seems I've
found the pattern. Here's the recreated project to show the problem (the idea
is to check whether the Caps Lock key is down when a shortcut has been
pressed); I've tried to make it as simple as possible:
In a blank project, directly on the main window, add a
CarbonApplicationEventsMBS object (name it CAE1); in Window1's code, add a
property (chk As CarbonHotKeyMBS). In the open event of the window, put this:
chk=new CarbonHotKeyMBS
chk.AddKey(126,256+4096,OSTypeFromStringMBS("MU "),658) //Command-Control-Up
Arrow
CAE1.Listen
And in the CAE1.HotKeyPressed event, put this:
if Keyboard.AsyncKeyDown(57) then //Is Caps Lock key down?
System.DebugLog "1"
Else
System.DebugLog "0"
end if
Run the app and try: Command-Control-Up Arrow with or without Caps Lock key
down. It makes no difference, you always get “0” in the Console (with Caps Lock
down, you should get “1”). Just to prove further, put the code of HotKeyPressed
in a timer, and it correctly reports “1”, meaning the HotKey somehow prevents
RB to check the Caps Lock key.
Tried with RB 2011.r4 under Mac OS 10.6.8. Can you reproduce this wrong
behaviour? Any fix could be done?
_______________________________________________
Mbsplugins_monkeybreadsoftware.info mailing list
[email protected]
https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
