Hi, my solution to this problem was to create a super pad layout that gw micro does have for review. Basically what it does it puts most of the window-eyes hot keys on the numpad. Amazingly I was able to get more commands define then gw micro had.
So it frees up the use of the insert key control shift keys etc for scripts. Another idea is at some point we need more prefix keys. Scrolled lock caps lock could be used. This way we get more possible places to put commands. The order keys are pressed could also be used. Like control shift and shift control. So lets say you have a program that uses control shift t. and your program uses it for something else well then control shift t will be a window-eyes command while shift control t will pass along the command to the program. Or if the command is not in use then shift control t could be used to tell window-eyes something completely different. Also left and right keys should be considered. None of these things are going to happen for 7.0 but I hope they are considered for later version. Just my thoughts. From: Jeff Weiss [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2008 7:01 AM To: [email protected] Subject: script hotkey conflicts I am really enjoying the new beta and the many scripts which have been written. I am writing this, so that we as Window-eyes users, might think of some ways to minimize conflicts when assigning hotkeys to scripts. I am only thinking of global scripts because if a script only runs in a certain application, the script author will certainly assign hotkeys which will not conflict with parts of the main application. Now, I know that the hotkeys that are assigned can be changed, but I think there are some things which will minimize conflicts: 1. control-whatever or alt-whatever should generally not be used to launch global scripts. One conflict that I have seen is control-f1 for the context help script. This key is used in WordPerfect to launch the spellchecker. 2. If possible, only one hotkey should be used for each global script. Now, I am not talking about hotkeys that are used after the script is launched--just the hotkey that launches the script. I think that the options from within script manager could better be used to set preferences for each script. 3. Scripts should be launched with hotkeys that have at least 2 modifiers, such as insert-control or insert-windows or alt-windows. I know there will still be conflicts, and we can always change the hotkeys, or use the insert-b to bypass these keys to send a key on to the application, but I thought some guidelines might help. Please, don't think I am trying to cause trouble, and I'm sure that many of you will have some ideas about this. Ultimately, this will be upto GWMicro and the script authors. What do you think? Would some type of guidelines like this help? Do you have any other ideas for such guidelines? Jeff Weiss If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [EMAIL PROTECTED] and include leave gw-info in the body of the message. If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [EMAIL PROTECTED] and include leave gw-info in the body of the message.
