why don't you just redefine them to something else for the set file for that program. For example you could put all the mouse commands on windows numpad combos. . Jim Grimsby Junior. Please feel free to contact me at anytime using one of the below methods. Skype: Jim.Grimsby 909-498-4711. E-mail: jgrim...@roadrunner.com Windows live messenger: jim.grim...@att.net
-----Original Message----- From: Bryan Smart [mailto:bryansm...@bryansmart.com] Sent: Monday, September 28, 2009 9:01 AM To: gw-scripting@gwmicro.com Subject: Automatically by-passing WE hotkeys I'm scripting for an application that requires the use of the keypad in its main window. The app expects to receive keys such as home, end, page up, page down, and the arrows when the keypad keys are pressed. I can voice everything in the main window, so not being able to use the WE cursor there isn't a big loss. However, I'd like the WE cursor to be available in this app's dialogs and other parts of the user interface. What is the best way for me to temporarily suspend just the keypad hotkeys? I can use a ConnectEvent call to watch for an Activate event in the overlap area to detect when the foreground window has changed, and I can evaluate if I'm now in the main window or not. However, the only way to fix the keypad keys seems to be to unregister all of those WE hotkeys when the main app window gains focus, and then to reregister them when the main window loses focus. This can't be the best way, though, as, when I reregister the hotkeys, I can only register them back to what I think they should be, and, I believe, the user can redefine these. I'll have, therefore, potentially messed up the user's default assignments. Any suggestions are welcome. Bryan
