sgp: > Perhaps someone could summarize the key reasons for using > keytrap and not powerpro hotkeys?
As well as the things drmwpdc and David mentioned... The latest version of PowerPro has narrowed the gap, for example the new exec.tracekey() replaces the need for keytrap.scanmode, but there are still good reasons for using keytrap: (a) it allows more detailed control of what will trigger a hotkey (b) potentially more possible hotkeys from extra modifiers (c) it provides a more powerful version of the *keys command (d) it has more keyboard diagnostic/enquiry tools Those advantages are achieved by: - you can use keytrap.sendkeys as an extended version of *Keys, sending a keystroke specified as a Scan Code, or as a Virtual Key code, or both - plus you can send keydown or keyup alone, rather than only being able to send down+up - you can use keytrap.sendkeys as the command in a keytrap hotkey or a Powerpro hotkey, thus remapping the keyboard - you can set either keydown or keyup, to be the hotkey's trigger and specify whether a hold-down will auto repeat - choose whether a hotkey is eaten or passed through to the active window, as well as doing the hotkey's command - specify for individual hotkeys whether it waits for the modifier(s) to be up before executing the command (in PP native hotkeys this is a general setting for all hotkeys) - you can create more modifiers; for example PP native hotkeys can now use RightCtrl down-up as a hotkey, but keytrap can use it as an extra modifier. If you use the Right varieties of Ctrl, Shift, Alt and Win as extra modifiers, in addition to the usual 4 left modifiers, that is potentially several thousand extra hotkeys (permutations of up to 3 modifiers out of 8, combined with any of the 100 normal keys) if you can remember that many hotkeys :) In fact any key can be a modifier so there are more than a million possible hotkeys. - you can reset phantom pressed keys (all keys or a specified key) meaning keys which the system thinks are still pressed when physically they are not held down. - you can get a list of currently pressed keys - return either the SC or VK of the next key pressed - enable/disable Ctrl-Alt-Del (useful for "kiosk" situations, demonstrations, classrooms, etc) - specify multiple semi-matching hotkeys, then use the optional "stop" parameter, so one keypress might optionally trigger more than one of your keytrap hotkeys Of course, I don't personally use all those things regularly but if you have an unusual need or a difficult problem with customising a keyboard, keytrap probably has the feature needed to fix it. In summary, as well as providing more flexible hotkeys it can be used in scripts to simulate more kinds of keyboard actions. 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/
