Anti-Autoclick function (use rapid fire button on gaming mouse for something else)

[rensek]

Please fill in this template when posting!
XMBC Version: 2.20.5
Installed or Portable version: portable
Windows Version: Windows 11 Version 23H2 x64
Mouse Information (brand/model): Battletron RGB gaming mouse
Relevant Computer Information (CPU, RAM etc): i7 8700K, 16G
Did the problem occur after an upgrade of XMBC? (If so, from what version?): no
Did the problem occur after a Windows update/upgrade? (If so, from what version?): no
How long have you used XMBC?: 1 day
What language and keyboard layout do you use in Windows?: german qwertz

Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).:

Hello everyone,

I have a cheap gaming mouse that came with an extra rapid fire button next to the LMB. Pressing this button sends repeated LMB presses, you get the idea. This function of course is hardcoded into the circuit of the mouse and the button is not registered as an individual button by Windows. Now, while this button might be useful for some gamers, I would rather use it as an extra button of my choice. So my question is if it's somehow possible for XMB to detect when the mouse sends 3 (or maybe 4, 5...9) rapid LMB clicks and then lets me configure a different function for that key? I hope it is clear what I mean, basically an anti-auto-clicker.

Sorry if the topic has been answered before, I checked the FAQ and did some basic searching but found nothing.

Thanks,
Seb

[phil]

I know what you mean, I have such a mouse (I have far to many mice!). But its certainly not possible right now to do that in XMBC and I really don't think it would be worth the effort (its a significant complexity) to try and implement such in a reliable fashion.

For starters, ALL left clicks would need to be blocked until XMBC could determine if there is more than one or not, and then re-injected (simulated) if it determines it was only one click. That not only introduces (potentially significant) lag but also it wont work with anything that detects/blocks simulated input, rendering the left button effectively broken.

Similar tactics have to be employed for button chording or button held (which is why I have previously advised against using those on the left button, or at least being aware of the trade offs!).

[rensek]

Sorry for the late reply, I couldn't access my computer for a while. Your eplanations make perfect sense, it would probably be a nightmare and cause more trouble than helping, esp. with LMB. Could have figured this out by myself...

I might look into AutoHotkey and see if I can come up with a script that somehow works. I'll post it here if I'm successful.