If you do this in your script, you'll be able to get the hotkeys that
are taken on whatever system your script is running on. Besides, the
majority of script hotkeys are user definable, so having a static list
somewhere doesn't really gain you anything.
Aaron
On 4/23/2010 4:50 PM, David wrote:
OK, Aaron. But, won't this only tell me what hotkeys are taken on my
actual system? It doesn't tell anything as to which hotkeys are being
used by any of the scripts, that are available on SC, and not
installed on my particular system, does it? So, then, there will be a
chance, that I am releasing a script, that conflicts with another
script, that others might find quite interesting. And, it was to avoid
this kind of conflicts, my idea came up. It is easy enough to keep
track of not conflicting with hotkeys on your own local computer, but
you might only be runing 20scripts, whilst there is close to ten times
as many available.
----- Original Message -----
*From:* Aaron Smith <mailto:[email protected]>
*To:* [email protected] <mailto:[email protected]>
*Sent:* Friday, April 23, 2010 10:43 PM
*Subject:* Re: Which hotkeys are taken
You should iterate through Keyboard.RegisteredHotkeys, as that
will list all script hotkeys in real time (or at least those
registered through Keyboard.RegisterHotkey).
Aaron
On 4/23/2010 4:34 PM, David 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
<http://www.spamfighter.com/len>.
We are a community of 7 million users fighting spam.
SPAMfighter has removed 1548 of my spam emails to date.
The Professional version does not have this message.
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
