So I could use this, for example, to create a dedicated volume control device out of a spare mouse? It would involve mapping the directions of the extra mouse's

So I could use this, for example, to create a dedicated volume control device out of a spare mouse? It would involve mapping the directions of the extra mouse's wheel to VK_VOLUME_UP/DOWN and to assign a no-op macro to the x/y axes so it does not interfere with the normal mouse? Edit: for your information, I couldn't get any mouse triggers to work in a reasonable time. If someone else does, just reply here, please. Sending volume keycodes in reaction to a different keyboard event (e.g. pressing scroll lock/pause) worked somewhat. I had to send them with CreateObject("WScript.Shell").SendKeys(chr(&hAF) as scripted action though. VK_VOLUME_UP/DOWN is not defined, use characters &hAF for "up" and &hAE for "down".