> Both pproconf.exe and powerpro.exe's exec.tracekey > worked perfectly here for every key -- showing the > same results as other tools such as keyview.exe.
Thanks, I will go ahead and implement hot keys which respond to both vk code and scan code. >> > I have noticed in the past, when setting hotkeys for those > keys' VK codes in pproconf, both things would happen. > This was also the case for the new test versions. PowerPro is doing the best it can to prevent this. It does turn off the normal function of most keys which are defined as hot keys. But it seems that for the above, and others like F1 and F12, something else is recognizing and processing the key before PowerPro gets a chance to tell the system not to process the key further. I don't know how to prevent this. The best I can think of is to use your registry approach to assign them no command and then use PowerPro to assign them another function. 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/
