Hi Jeff, Thanks a lot. I guess I didn't examine the created stuff enough. The only thing is I like to use ClientInformation.ApplicationProcess instead of the overlap.
Vic -----Original Message----- From: Jeff Weiss [mailto:[email protected]] Sent: Wednesday, June 22, 2011 4:19 PM To: [email protected] Subject: RE: Advanced hot key topics This can be done in the We Script FrameWork Wizzard. Here are the two choices for either global hotkeys or local hotkeys: ' use for global registered hotkey Set registeredHotkeys("Key01") = Keyboard.RegisterHotkey(SO_HotkeyManager.Key("Key01"), SO_HotkeyManager.Data("Key01")) ' use below for an application specific hotkey Set registeredHotkeys("Key01") = Keyboard.RegisterHotkey(SO_HotkeyManager.Key("Key01"), SO_HotkeyManager.Data("Key01"), ClientInformation.Overlap) Note: There is only one line under each comment. They may get split in the email. Jeff Weiss -----Original Message----- From: Vic Beckley [mailto:[email protected]] Sent: Wednesday, June 22, 2011 2:53 PM To: GW Scripting List Subject: Advanced hot key topics Chip, Have you covered the advanced hot key topics. I know you mentioned it in an early class, class 10 I think, but I can't find any reference to it later. I haven't been able to listen to all your classes, though. The problem I am having is that it seems the WEScript Framework makes all the hot keys global. I want to limit them to a specific application that the app is associated with. What is the easiest way to do this. Thanks for any help on this and your classes are great. Vic
