Highrez

XMBC Version: v2.19.2
Installed or Portable version:: Installed
Windows Version: Windows 11
Mouse Information (brand/model): Zelotes F-35 (Plug and Play)
Relevant Computer Information (CPU, RAM etc):
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?: 2 days
What language and keyboard layout do you use in Windows?: Azerty (French)

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).:

Hi,
It seems the middle click button inactivates my MB4, then I cannot set any chording with Middle click button+MB4. All others buttons work fine.
At the setup screen, if I click on the middle button + Mouse button 4, then only the middle button line is highlighted in orange. Whereas if I click on the middle button + any other mouse button, the both lines are highlighted.

Anyway, thanks for this software, I've just started to use it but it seems very useful

All the best
Mut

I have the same issue (both on the stable and 2.21 Beta 37)

While the middle button is held, XMBC loses Button 4, and shows its status as up, no matter what I'm doing with B4.
The same is true for RMB and B5.

In my case I'm trying to set B4 to be Ctrl, so I can hold Ctrl while dragging with middle mouse.
The immediate work around is to use B5 instead of B4.D

FYI:
1) 2.21 Beta 37
2) Win 7 x64 Home Premium
3) 5 (Kensington K75520)
4) Generic HID-Compliant Mouse (Microsoft Mouse Driver V 6.1.7600.16385 - 21.06/2006)
5) No mouse configuration software installed (couldn't install KensingtonWorks on Win 7 - hence using XMBC)
6) As above.

Can only imagine this must be device specific as it does not seem to be a problem with any of my mice...
That includes logitech, Microsoft and generic (trust) mice Ive check with here.

Just to be sure XMBC is not seeing anything, turn on debug logging (settings -> updates & logging tab) then OK and APPLY that....
Then press MB4 a few times (on its own) followed by holding MMB and press button 4 a few times (note the time you do this).
Turn debug logging back off.
Send me the debug log (can be opened/accessed from the updates & logging tab) and let me know the time you did thi test so I can find it in the log (debug log is *very* verbose)...

That will at least show us the actual messages XMBC is getting from the Windows mouse subsystem. I suspect it simply wont be seeing the MB4 while MMB is held down - and if that is the case, there is nothing that I (or XMBC) can do about it.

Regards,
Phil

PS. Apologies to the OP - I clearly missed this the first time round!