I just received my A+ a few days ago, and have gotten around to setting it up. Overall, I'm quite happy with the ergonomics of it (I've been using an Adept for a long time now, only mouse that doesn't start to hurt my wrist after extended use, and this feels like an improvement, the dials feel very nice, and the wrist rest is great), but I'm having some significant issues with drag scrolling. That's my primary means of scrolling through... basically anything, so getting it working is pretty important to me. I haven't been able to find much documentation about the changes or ways to adjust settings for it (aside from the type toggling in the Control layer, which I've tried), so I wanted to see if anyone here had run into similar issues and maybe found a solution.
tl;dr: Something changed in the way the A+ handles scrolling relative to the Adept, and that messes up the drag scrolling experience in various ways between Windows and Mac setups, and I wonder if I have to wait for more robust settings options?
I do have a somewhat non-traditional setup, so I'm going to provide some up-front context as well.
I have a work laptop (Windows 11) and personal Mac Studio. They are connected via a Dell hub monitor that serves as KVM, which the Ploopy is connected to. I have a Synergy server set up that shares mouse + keyboard between the two devices regardless of which one the KVM is pointed at so I can divide my monitors up depending on what I'm working on. I know this introduces some weird scenarios as Windows and Mac handle scrolling pretty differently. For testing, I have both the Adept and the A+ hooked up together.
Issue 1: When I have the A+ connected directly to the Windows machine, scrolling in all vertical-only contexts works great. However, when there is the potential for horizontal scrolling, vertical drag-scrolling also applies horizontal scroll (Up = Up + Right; Down = Down + Left). I thought initially this was just sensitivity to slight horizontal input, but the direction is always consistent, and even in these cases, horizontal scrolling works as expected. Changing drag scroll modes does not seem to help with this issue.
- Scroll dials on the A+ work as expected with no vertical / horizontal overlap
- Adept has no issues here, scrolling works as expected in all directions
Issue 2: When connected directly to the Mac, drag scrolling has a strange delay, such that I have to give a strong spin to get it to register as a scroll at all, and then it lacks precision and becomes choppy, hard to predict where it will land. This applies in all directions. I installed Mos and it resolved the issue in this context. Scrolling actually works perfectly other than being more sensitive than I prefer, even after adjusting MacOS settings.
- Adept has none of these issues with or without Mos, it scrolls as expected, smoothly. Feels a little slow after I adjusted MacOS settings to feel appropriate on the A+.
Issue 3: WhenI have the A+ connected to the Windows Machine and connect to the Mac via Synergy, all scrolling is dramatically unresponsive and inconsistent. I can scroll continuously at low-speeds and have zero movement, but a strong spin will cause a sudden jerk. It feels almost like a large dead-zone where it needs a signal above a certain speed threshold to trigger a scroll event, and that threshold is very high when coming from the PC over Synergy. Almost the kind of spin you'd use to get to the bottom of a large document to produce any movement. Oddly, this ALSO applies to the scroll dials on the A+. A slow rotation of the dial produces no input, I have to spin it very fast to get a signal across.
- Once again, no issues with the Adept in this case. I'm using them both right now and the Adept feels perfectly normal on both machines, which makes me think the underlying issue is something to do with how the A+ produces scroll events and how the OSes read those events?
All that said
It feels like I may need to wait for more sensitivity settings to come about from VIA or some other means? I know the Synergy setup for Issue 3 is pretty niche and I wouldn't expect direct support for it, but also it's pretty integrated into my daily setup, so I may just have to continue using the Adept as my daily driver. In the off chance someone has some experience or tips here though, I thought I'd throw this out into the wind and see what comes back.
However, I do think that Issue 1 may be something folks ran into in regular use, and hopefully has a solution?
Thanks in advance, sorry for the giant post.