AutoHotkey Community

So how would you integrate these HID raw data outputs - once you found them - into your autohotkey.ini?
The focus should be on an easy and simple integration for non-advanced users.

How I would integrate raw input and the easier/simpler method for non-advanced users are entirely different. For instance, this is "optimized" for the chat button on my mouse (since it's the only button I need to detect):As you can see, there's barely any separation of implementation from the assigned action, so it isn't user-other-than-me-friendly.

What I want to know is: how would you like to integrate raw input within your scripts? For instance,
would be the most abstract, but obviously won't work since it doesn't say which device, or what "chat" is.

Perhaps something like this?:Pattern could be a regular expression, or a simple string such as "030000E200" (which would be my mute button.) I suppose for readability, optional spaces could be included: "03 00 00 E2 00".

"Why use a regular expression?" -- If I press mute while holding chat, I get the message "03 BC 01 E2 00", which is a combination of chat (BC 01) and mute (E2). So, for instance, I could say "^.{6}E2.{2}$" and that would match "030000E200" (mute), "03BC01E200" (chat+mute, or mute+chat), etc.

I suppose regular expressions aren't for "non-advanced users," though.

Hi lexikos, sorry for the delayed answer, I was out of town for the last days.
First of all, taking up Micha's comment, there should be a switch to turn HID support of, if not needed - to reduce the space autohotkey needs at runtime. There should also be a switch to set the HID-device to listen to or disable input from certain devices. Perhaps like this:
Second, I would prefer to keep the syntax that autohotkey uses for keys and use it accordingly for HID devices. Something like this:

To facilitate the learning process for the user, the section "key history and skript info" of autohotkey should contain 1) the necessary HID strings (in this case 030000E200)and 2) the device the string was obtained from.


Would be great if we could get this working and our comments find their way into the program...

Since I posted, I've been working on a RawInput function-library script, which I will use to make a (hopefully) user-friendly method of accepting raw input in a script. It won't be as easy as "hotkey::", but perhaps as easy as the hotkey command. (It'll need to be called from the auto-execute section to associate devices/data with labels.)

To test the functions, I wrote a GUI script (which will also be useful in determining what data a device sends.)

That shows all of the ways a device can be identified (atm.)
Unfortunately, it isn't easy to get a (useful) readable device name. Of some use, the Device Name shown on the GUI (and by Micha's script) contains a hint to a registry path. For instance,
The registry key for this device can be found atUnfortunately the only "readable name" I see is "HID-compliant consumer control device." Not very useful.

The Vendor ID (VID) and Product ID (PID) identify the device (in this case as a Logitech MX610.) To get a list of handles to matching devices, I can do:This gets the top three devices in the screenshot above. To identify the specific device I am after, I can do one of:
#DisableHIDSupport seems redundant, since OpenHIDforInput() would be required to tell AutoHotkey to register a device.
I'm not sure exactly what space would be used, other than the space for each HID-hotkey, and the memory used by the raw input code itself.

Heh, it just occurred to me that whileis not a valid hotkey (at least, "doesn't exist in the current keyboard layout"),are valid labels. Still, I think it would be best to include some indication of which device should trigger the HID-hotkey/label. (That is, if it were automatic/built-in.)

The level-of-ease I'm eventually aiming for is something like:

• Open the GUI.
• Select a device (or all devices.)
• Press a button. Assuming it triggers an input event,
• Click the input event. This should generate code for quick insertion into a script, and possibly more specific details, like a filter to identify the device, and the data string alone.

Example code:I'd use OnRawInput(), but that wouldn't be function-library compliant.

What has been delaying the script is this: a string like "030000E200" doesn't seem like a generic enough way of identifying a button. Additionally, it doesn't seem to provide much benefit over the existing scripts. For instance, where does the script you mentioned earlier fall short?

I have been playing with Raw Devices today, using my USB keyboard. I managed a limited success - I can get a list of HID devices, I can intercept (using WM_INPUT) any of them, and I can capture events for many keys on my keyboard. Unfortunatelly, AutoHotKey is able to capture those keys as well. I couldn't get a single "real raw" input from my keyboard (that is, a sequence of bytes similar to that you listed above) - all WM_INPUT messages came in the form of "slightly translated" RIM_TYPEKEYBOARD, none as "real raw" RIM_TYPEHID. Unfortunatelly, it doesn't seem like I can capture the extra keys - not even when I intercept the whole UsagePage 1

I hope I will have a better luck with my MX1000 (when I come back home where it sits). If I could capture at least SOME of the extra keys, it would be nice.

I used Lexikos's script for my remote control.
The remote control add a HID and a JoyStick in my PC. The script can get code from Joystick (Usage=5 and UsagePage=1).
But it can not get code from the HID (Usage=0 and UsagePage=65280).



Can you help me?

Thank you a lot.