> Well I found a solution to this problem which has bugged me ever since > XP was installed. I think there is a problem with Keytrap setting > Numlock on and off, I could never get it to work at all.
This is actually a feature under the GUI tab (for capslock, scroll lock, and numlock - numlock is the only one that doesn't work). You are supposed to be able to choose either to lock it on, lock it off, or do nothing. I know the feature used to work years ago, but it was broken at some point and now only the scroll lock, and caps lock ones work in XP. Bruce has looked at this several times, but has never been able to find the problem with why it doesn't work. Bruce: Can you look at this one more time? I played with it a little more, and noticed a couple things: - The function will toggle (turn on if it was off/turn off if it was on) the numlock button when you hit ok or apply with the checkbox checked (full check or grey check) and it has been changed during that configuration session. - If checkbox is unchecked, numlock status isn't toggled on pcf reload. - Weither grey-checked or full checked, numlock always toggled when you hit apply if the checkbox has changed state in that configuration session. Test scenario: Use the apply button on the command list tab screen to make the pcf load into powerpro. - Set the checkbox for numlock status to unchecked. Hit apply. (numlock doesn't change) - Set the checkbox for numlock status to dark checked. Hit apply (numlock led toggles) - Set the checkbox for numlock status to grey checked. Hit apply (numlock led toggles) - Click checkbox 3 times so it is back to grey checked. Hit apply (no change to numlock led) - Click checkbox so checkbox is dark-checked. Hit apply (numlock led toggles) Summary: Numlock doesn't change if: you don't change checkbox during the configure session or if you have checkbox unchecked. Numlock toggles status if: You change the checkbox state to a different checked state (grey to black or black to grey or blank to a checked state) during a configure session it toggles the numlock no matter it's current state when you hit apply. If I had to guess, it's like a bit isn't getting in the pcf map (hope the lingo isn't getting mangled too much) to tell powerpro what the state the numlock key should be forced into (either on always or off always). ------------------------- > However I found a freeware program that will force Numlock to be in > either state: http://www.rjlsoftware.com/software/utility/numlock I guess this is a good workaround if the powerpro GUI function can't be gotten working. However, even now if you want to force numlock to be in the on state at any time, say during powerpro startup you should be able to do that with keytrap: If (keytrap.GetKeyState(1,144) == 0) Keytray.sendkeys(69,144,0) Keytray.sendkeys(69,144,1) However win.debug(keytrap.GetKeyState(1,144)) Seems to also be broken, and unable to see the numlock status with keytrap 2.3 under XP. Does anyone else see this? ------------- I think you should also be able to do it with the AU3 plugin as well with the command au3.Send("{NUMLOCK on}") But that didn't seem to work. Maybe Alan Campbell can help with the syntax of the command. David Troesch | Atlanta, GA | ICQ# 2333123 "Good choices come from experience. Experience comes from bad choices." Funstuff: Doesn't expecting the unexpected make the unexpected become the expected? 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/
