Special Keys
If your keyboard or mouse has a key
not listed above, you might still be
able to make it a hotkey by using the
following steps (requires Windows
XP/2000/NT or later):
- Ensure that at least one script is running that is using the keyboard
hook. You can tell if a script has
the keyboard hook by opening its main
window and selecting "View->Key
history" from the menu bar.
- Double-click that script's tray icon to open its main window.
- Press one of the "mystery keys" on your keyboard.
- Select the menu item "View->Key history"
- Scroll down to the bottom of the page. Somewhere near the bottom are
the key-down and key-up events for
your key. NOTE: Some keys do not
generate events and thus will not be
visible here. If this is the case, you
cannot directly make that particular
key a hotkey because your keyboard
driver or hardware handles it at a
level too low for AutoHotkey to
access. For possible solutions, see
further below.
- If your key is detectible, make a note of the 3-digit hexadecimal value
in the second column of the list (e.g.
159).
To define this key as a hotkey, follow this example:
SC159:: ; Replace 159 with your key's value.
MsgBox, %A_ThisHotKey% was pressed.
return
Reverse direction: To remap some other key to become a "mystery key",
follow this example:
; Replace 159 with the value discovered above. Replace FF (if
needed) with the
; key's virtual key, which can be discovered in the first column of the
Key History screen.
#c::Send {vkFFsc159}
Alternate solutions: If your key or mouse button is not detectible by
the Key History screen, one of the
following might help:
Reconfigure the software that came
with your mouse or keyboard (sometimes
accessible in the Control Panel or
Start Menu) to have the "mystery key"
send some other keystroke. Such a
keystroke can then be defined as a
hotkey in a script. For example, if
you configure a mystery key to send
Control+F1, you can then indirectly
make that key as a hotkey by using
^F1:: in a script.
Try DllCall: Support for Human
Interface Devices. You can also try
searching the forum for a keyword like
RawInput*.
The following is a last resort and
generally should be attempted only in
desperation. This is because the
chance of success is low and it may
cause unwanted side-effects that are
difficult to undo:
Disable or remove any extra software
that came with your keyboard or mouse
or change its driver to a more
standard one such as the one built
into the OS. This assumes there is
such a driver for your particular
keyboard or mouse and that you can
live without the features provided by
its custom driver and software.
It's a good solution, but I would prefer a more simple one. Since the stop, play, next and previous buttons can be configured to Winamp, I would expect that the start button also can be configured somewhere... – Karsten – 2010-02-03T09:40:42.703