> No, sorry, I don't have any more ideas for making it work. What id > does it look at the keyboard state and if the numlock is in the wrong > state, it sends numlock to change the state.
Whatever is testing the state must be broken then, because no matter what the state is, if you change the checkbox from grey checked to solid checked (or vice-versa) and apply the change the numlock state always toggles. Maybe it's the same reason this always returns 1? win.debug(keytrap.GetKeyState(1,144)) I noticed at the bottom of the vkcode.htm file that comes with the keytrap plugin these listed: E0 45(69) 90(144) "Num Lock" 3A(58) 14(20) "Caps Lock" 46(70) 91(145) "Scroll Lock" Where "If a scan code is preceded by E0, check "Ext" in pproconf - it's an "extended" code." I noticed that capslock, and scrolllock functions under the GUI tab work fine, and they are not listed with the E0 code. Maybe that's been the problem all along? Is there something special that needs to be done to read the "extended" code keys in checking it's state? David Troesch | Atlanta, GA | ICQ# 2333123 "You are the only real obstacle in your path to a fulfilling life." Funstuff: Enter any 11-digit prime number to continue... 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/ <*> 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/
