Bizaro wrote: > If I select printscreen in the Key/Mouse dropdown than Print Screen works > as a hotkey. But, Print Screen is not recognized in Type key, also Print > Screen does not work as a hotkey if I enter VK, Scan and Ext. returned by > Exec.TraceKey() for the Print Screen key. Bug?
I would not call it a bug - just that it fails to provide special handling for the bizarre behaviour of the PrtScr key. All the other keypress viewers I have tested have the same problem with that key - which is not surprising because PrtScr sends unusual four byte strings for each of its Down and Up scan codes. According to microsoft's "Scancode.doc" PrtScr produces these unusual combinations of scan codes in response to a press with various modifiers: unmodified Make: E0 2A E0 37 unmodified Break: E0 B7 E0 AA LCtrl or RCtrl + LShift or RShift + Make: E0 37 LCtrl or RCtrl + LSHIFT or RShift + Break: E0 B7 LAlt or RAlt + Make: 54 LAlt or RAlt + Break: D4 Note: Pressing and releasing PrtScr produces approximately: Shift Down, PrtScr Down, PrtScr Up, Shift Up except that a real Shift is plain 2A, not E0 2A There is no listing in MS docs for "E0 2A" as a scan code used alone -- the only place I have seen it used is in that exceptional combination. Note: Alt+PrtScr produces scan code 0x54 which is the scan code listed for SysReq. So it's not surprising that entering a scan code did not work. I guess you tried VK 0x2c(44) and SC 0x37(55) with Ext checked, which is not the complete scan code. > Bug? It depends how much you expect. It would need extra code to handle when a user types 55 in the scan code box when Ext is checked and show a warning message that this will produce unexpected results. I think that is too much to expect from pproconf - instead the user should not type faulty codes (Ext + dec 55 is not the correct Scan Code for PrtScr). Similarly I think it's too much to expect Exec.TraceKey() and pproconf's "Type key" to record a PrtScr keypress correctly, considering that none of the other available tools for viewing keypresses can do so. Again it would need some extra code to watch for this exception and treat it differently from all other keypresses. Anyway there is no need for setting a scan code as the hotkey. There are two ways which do work, to specify PrtScr as a hotkey: either select it from the dropdown, or use "Enter virtual key" (vk decimal 44) without "Use scan". Maybe PowerPro Help could mention that you cannot use pproconf's "Type key" feature for PrtScr. If it's documented, it isn't a bug :) -------------------------------------------------- Caution: there is a similar tangled mess in the scan codes sent for the Insert,Delete,Home,End,PageUp,PageDown and arrow keys and their equivalents on the numeric keypad. Instead of trying to untangle what happens when NumLock is/isn't on and Shift is/isn't held down, just avoid using scan codes to specify hotkeys and use the drop-down key selector in pproconf or only the VK number. I haven't attempted to test those keys with various states of numlock, shift, etc, because I don't care - we don't need to use their scan codes. IMHO, the scan code method of setting a hotkey is best kept for where it is necessary, such as the extra multimedia/internet keys which return the unspecific 255 as their VK code. 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/
