How do I stop input queuing?

[Mikk]

XMBC Version:
2.19.2:

Windows Version:
8Windows 10 20H2:

Mouse Information:
Logitech G502 Hero:

Relevant Computer Information:
Threadripper 3970x,G.Skill 4000MHZ 64GB, TRX40 Aorus Master:

How long have you used XMBC?
A couple of days.:

What language and keyboard layout do you use in Windows?
Keyboard Danish - Windows English:

I am using XMouse Button Control because the Logitech software does not permit me to rebind MouseWheelUP/Down. I am using the mousewheel to send inputs into video games. The problem I am having is that the inputs get queued up so that the inputs continue even after I stopped scrolling. If I scroll for a while and then stop the inputs can continue for more than 30 seconds. Is there a way to stop that form of input queuing?:

Thank you in advance for taking the time to look into this.

//Mikk

[phil]

Have you tried the "Ignore repeated remapped vertical/horizontal scroll" on the options tab? That's the only thing I can think of that might help here.

[Mikk]

I tried it and it helps a littlebit. The optimal situation would be that the input stops when I stop spinning the wheel. But that might not be possible then.

[Mikk]

Ok I played a little around with it and now it works when I set it to 2 MS. Thank you very much for your help.

[phil]

I'm glad you found a setting that worked, as that's the only option currently in XMBC.
Because the wheel (and tilt) are not buttons that send discrete down/up messages, its more complicated because you dont actually know that scrolling has stopped (for sure), you can only assume it by the lack of a new scroll message in a given time. What this option does is essentially ignore messages that happen too quickly, so as not to bother adding additional entries to the send input queue which in turn means said queue is processed more quickly and stops closer to you stopping scrolling.

XMBC does not have the ability to kill the single simulated input thread/queue when you stop scrolling - and I'm not sure that would be feasible (a simple change) because there may be other things in that queue that you wouldn't want to remove - and also you still need to know (guess) when the scrolling has really stopped!