Hi Bruce 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.
My Logitech Access keyboard has seven keys which send unique VKs and fourteen which send VK 255 (two unusual keys called Webcam and Messenger-SMS, plus the F1 to F12 keys when F Lock is toggled off). It seems the seven with unique VKs simply trigger common system jobs. They all work without the Logitech driver. All keys with vk255 do not trigger normal system routines. None of them work when the driver is not installed. However they all send unique scan codes. There is one thing I should describe: Regarding the keys which work when the Logitech software is NOT installed, because they are sending codes which the system responds to [for example the Search key opens the Windows file search window, the EMail key opens my default email program (TheBat), Media opens WinAmp, MyHome opens my default browser (Opera) at its default Home page] 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. For example when I press Media (which I know has sc: 109 ext and vk: 181) the test pproconf reports the correct codes and so does exec.tracekey, but WinAmp also opens in both tests. The same thing happens with Keyview.exe - it does not eat the codes which are sent by these special Logitech keys. I don't have an opinion about whether pproconf's "Type key" edit box should eat the codes of the pressed key, or allow the system to react as normal until the user has clicked Apply to enable the new hotkey... similarly I don't know whether exec.tracekey should eat the codes while it is enabled... but I do think it's important to eat the codes after they have been set as a hotkey, and Apply is clicked. Some hotkey apps have an option: when executing the hotkey command either eat the codes or not (so other apps may also do their thing). Quote: [if this option is checked] "This hotkey's native function shouldn't be suppressed (hidden from the system) when the hotkey fires" I don't think that option is important to provide. IMHO if that option is not offered, then the default should be to eat the codes. If a user wants the system's normal reaction as well as the hotkey commands, he can add them as More commands. For example when setting a hotkey for the EMail button I could add TheBat.exe to More commands if desired. Alan 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/
