--- In [email protected], [EMAIL PROTECTED] wrote: > > > Note keytrap should be able to do this, but in my testing this: > > win.debug(Keytrap.GetKeystate(1,144)) > > Always reports 1. > > > > But win.debug(Keytrap.GetKeystate(1,20)) does report the state of the > > capslock key properly. > > > > It's like the numlock key in windows is handled slightly > > differently than > > the capslock or scrolllock keys. > > I noticed that when testing the keys in keytrap, numlock is the only one of > the 3 "togglable" keys (numlock, capslock, scrolllock) that has ext=1 (is an > extended key). I've always thought that it has something to do with the > problem.
I don't think it's an extended key problem as GetKeyState uses vkcodes, not scancodes. Anyway, I noticed that if I turned on the check box "Disable numlock" in pproconf, Keytrap.GetKeystate(1,144) indeed always returned 1 (:this was the first time I ever touched). Sean Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/power-pro/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
