Yes, you're right about what a mix it can be. It's why (I think), they created the scripts menu; to allow us to have another way of interfacing with our scripts. I personally find the menu more desirable to use in most situations, because you can see all your options for a given script (without having to go through help and into the hotkey manager). it doesn't work best in all situations, but there are many places where script authors could convert to using it.
Chip -----Original Message----- From: Jeff Weiss [mailto:[email protected]] Sent: Saturday, May 01, 2010 4:23 PM To: [email protected] Subject: Re: Which hotkeys are taken No, my script just shows you the assigned hotkeys in the currently active set file. I have loaded scripts where two scripts attempted to use the same hotkey. If one script has already registered a hotkey, that script will continue to function properly, while the second script will not. There is no warning error message. The easiest thing seems to me is that the user will just have to install a new script, read the help, and if the hotkey for the script does something else, one or the other will need to be changed. When you think about it, everybody's mix of scripts, and even customized Window-eyes hotkeys, and personalized system hotkeys are different. With so many scripts, there are bound to be conflicts. Jeff Weiss ----- Original Message ----- From: "Chip Orange" <[email protected]> To: <[email protected]> Sent: Saturday, May 01, 2010 1:52 PM Subject: RE: Which hotkeys are taken >I don't think though that either script will tell you which hotkeys are in > use by your current set of scripts right? I don't know about your script > Jeff, but Jamals says it looks at the shortcuts on the desktop and the > menus. > > It becomes even more confusing because some hotkeys are application > specific, and so may or may not even be a problem for you if they do > conflict, depending upon whether your script uses application-specific > keys > or not. > > I have always wondered if, you try and register a global hotkey, and > another > script is currently using it, whether the registerhotkey method will > return > an error or not. seems that it should, but I've never asked that > question, > and the docs don't say. > > Chip > > > -----Original Message----- > From: Jeff Weiss [mailto:[email protected]] > Sent: Friday, April 30, 2010 1:45 PM > To: [email protected] > Subject: RE: Which hotkeys are taken > > Jamal has a script called > Detect shortcut keys > Which will give you a list of all of the system hotkeys that are defined. > I have a script that I have just finished called WEHotkeys Which will give > you a list of all of the Window-Eyes hotkeys that are defined in the > active > set file. > I will be posting it shortly. > Jeff Weiss > > > > > -----Original Message----- > From: Kevin Huber [mailto:[email protected]] > Sent: Friday, April 30, 2010 12:10 PM > To: [email protected] > Subject: Re: Which hotkeys are taken > > Hi: > I believe there is already a script which will do that. The name escapes > me > right now, but you press a hotkey and it gives you a list of all the > hotkes > of the scripts that you are running. > On 4/23/10, David <[email protected]> wrote: >> When starting out on a new scripting project, it might often be a > challenge >> to find a good hotkey, that will be used by default to initiate the > script. >> Sometimes, you find yourself writing a script, that uses a hotkey, > that >> others wanted to use, or already are using, as well. Of course, when >> releasing a script, you want your default hotkey not to conflict with > any >> other scripts. >> >> I just thought, that it might have been an idea, if there was > somewhere to >> look up a list, of which hotkeys are already 'taken' or occupied by > default. >> How about a spot on the WIKI, or something? Or, could it even be so, > that in >> the process of registering and uploading a new script - or version of > a >> script - to the SC, you would have to fill in a field holding info as > to >> which hotkeys your script occupies by default. And then, the server > would >> automatically register these hotkeys in a list, that new scripters > quickly >> could access, and make sure that they pick an 'available' hotkey for > their >> project. >> >> Anyone have som feedback on the idea? >> >> -- >> I am using the free version of SPAMfighter. >> We are a community of 7 million users fighting spam. >> SPAMfighter has removed 1548 of my spam emails to date. >> Get the free SPAMfighter here: http://www.spamfighter.com/len >> >> The Professional version does not have this message >> > No virus found in this outgoing message Checked by PC Tools AntiVirus (6.1.0.25 - 6.14580). http://www.pctools.com/free-antivirus/
