Mouse Button 6 is not captured/seen [bug]

[rmateu]

Description

Mouse Button 6 is seen by Steermouse, however it's not recognized by MMF. Please note that issues was present also in app version of 1.X.

Steps to reproduce

1. Click add (+) in main screen
2. In capture window click/drag/double click with side button 6

Expected

• New button action

Actual

• Nothing

Context

Mac Mouse Fix Version: 2.0.0 Beta 1 macOS Version: 11.2.3 (20D91) Mouse Model: Microsoft Precision Mouse

Additional Comments

I suspect this is not MMF specific. But since it works with steermouse and bettertouchtool, I'm hoping there's a way. Feel free to switch to feature request.

---

Console Logs

https://pastebin.com/13vxcJtY

(from steermouse Device Analyzer)

0001-0002-01 01 00 ** ** ** ** 00 00 00 00 
--------------------
// Mouse Button 6
0001-0002-01 01 20 ** ** ** ** 00 00 00 00 
0001-0002-01 01 00 ** ** ** ** 00 00 00 00 
0001-0002-01 01 20 ** ** ** ** 00 00 00 00 
0001-0002-01 01 00 ** ** ** ** 00 00 00 00 
--------------------
// Mouse Button 4
0001-0002-01 01 10 ** ** ** ** 00 00 00 00 
0001-0002-01 01 00 ** ** ** ** 00 00 00 00 
0001-0002-01 01 10 ** ** ** ** 00 00 00 00 
0001-0002-01 01 00 ** ** ** ** 00 00 00 00 
--------------------
// Mouse Button 5
0001-0002-01 01 08 ** ** ** ** 00 00 00 00 
0001-0002-01 01 00 ** ** ** ** 00 00 00 00 
0001-0002-01 01 08 ** ** ** ** 00 00 00 00 
0001-0002-01 01 00 ** ** ** ** 00 00 00 00 

Crash Reports

–

[rmateu]

Just a note to say that v2 Click and drag is game-changer (insert take my money meme here). And I love the balance power and simplicity the new button capture UX provides: it accomodates both a geek like myself and I can explain it to someone over the phone.

I'll be creating feature requests and any bugs I find, but huge kudos on the app update.

[svintuss]

I have a somewhat similar bug: on Logitech Master MX3 For Mac side button press Is not captured by Mac Mouse Fix's capture dialog. It calls app switcher ribbon instead. I run MacOS 11.2.3 and 2.0.0b2

[noah-nuebling]

Hey guys thanks for the feedback, and I'm happy you like the new click and drag feature! :)

I suspect that the buttons that don't work on your mice send special events that aren't normal mouse button events, and that that's the reason that Mac Mouse Fix doesn't pick up on them.

I think that SteerMouse has custom code for supporting for a myriad of different devices, but I don't see any hint that BetterTouchTool does this, too, so maybe the problem is something else in @rmateu's case. This is all just speculation though.

I don't have the resources to go buy all models of mice that send different events and build special code for supporting them, unfortunately, so please don't expect full support for these devices any time soon.

However, this got me thinking about a possible system where other people can write little plug-ins for Mac Mouse Fix to add support for a new device. I think that could work really well, Mac Mouse Fix being a relatively popular open source project. But it would require a ton of work to build a framework for that and is definitely a long way off at this point.

Sorry I won't be able to fix your issues soon, but thank you guys anyways for the inspiration!

[rmateu-pricesmart]

Thanks for the reply. I'll investigate a bit more on my side with other examples.

A short term thing we could do is a compatibility list (?), where using something similar to your pretty Mac Mouse Fix Feedback Assistant, and get user reports on which mouses work, and any issues. That could feed a simple (static) section on mousefix.org. Count me in to help parsing the reports if it's something that sounds interesting.

[noah-nuebling]

I'd love for Mac Mouse Fix to have an official compatibility list, but I think it would be a lot of work to get it right and I'd personally rather spend the time I have working on the app because I think that's more fun and more valuable.

I haven't thought about this much but I assume that to make this really good you'd have to:

• Create a nice front-end for the feedback form
• Store the data on some server (I'm not using anything besides static GitHub Pages at the moment)
• Dynamically create a section on the website for displaying the data. This could be really hard because the website is currently just plain html and css. It's also the first html and css I ever wrote - it's absolutely abysmal. I think you'd probably have to move (part of) the site over to some framework like Vue or Flask to do this, and to make it really good you probably also want some fancier features like a search field to search for you device and a prompt to add a new entry if the search doesn't come up with anything, and probably much more that I can't even think of right now.

I just have the feeling it would be a really large amount of work.

That being said, I don't know much about webdev. If you or anyone else have a different perspective on this, please let me know! I'm very much open to changing my mind on any of this. Be it on the basic idea for the implementation or the webdev stuff or how much priority we should give to having a list of compatible devices on the website.

[truefalsename]

hey, I have the same issue too. The middle side button seems to be automatically set to fast app switch (same as alt+ tab). If I click it while hovering on the cross it switches to the next app.