3Dconnexion Forum

ngomes wrote: ↑Thu Jul 15, 2021 7:00 am

zachraven wrote: ↑Thu Jul 15, 2021 6:52 am What is the holdup getting software out of beta?

Getting the virtual keyboard feature working as in macOS 10.15 and older. In other words, emulating the stand-alone use of modifier keys.

While we wait for that, what about other fixes or features requested?

ngomes wrote: ↑Mon May 31, 2021 12:49 pm On Mac, there's nothing higher than restoring the virtual keyboard feature.

Meanwhile could you concentrate on other features too?

Every line of code has a cost per target platform . I hope you agree that using a core feature (3Dx menu) in two different ways, between two OS, is not so nice. What seems a little feature, in reality is 1 more click to perform an action. Changes by a lot the UX between Win and macOS. That said, I ...

It's still on the to-do list but it will take us a while before we can get to it. Restoring the user-experience in macOS 11 as we have in macOS 10.15 and older is the current priority. Added features (such as MAC-281) have lower priority. I understand, but, you’re working on restoring UX since mont...

Any news about MAC-281?

Smart Scrolling behaves differently between macOS (Catalina and Big Sur) and Windows.
On Win Smart Scrolling is much more natural, while on macOS is too much faster. This oddity is present using CMW on an iPad too, so makes me believe it's a CMW firmware 1.11 issue to address.

ngomes wrote: ↑Thu Mar 18, 2021 8:53 am If the driver and device are working as expected (although not necessarily as you'd like), please continue this discussion in a separate thread.

Ok I'll start a new topic, but, just to better understand, is it working as expected for you (3Dx staff)?

If it does not work for you, why not simply disable the feature? There's a check box in the "3Dconnexion" pane in System Preferences to disable "Smart Scrolling". If this isn't working, then that would be a bug in the new driver and we will need to look into it. Smart Scrolling ...

ngomes wrote: ↑Thu Mar 18, 2021 8:09 am From what I can see, the device is operating as expected and this isn't a driver problem in macOS 11.

Ok, so it's probably an old bug.
And, anyway, this virtual wheel spins too much. Needs more friction, or customizable friction... I already requested this in the past.

It's not infinite: it's implemented as an "inertial wheel with friction": the scrolling beings to "die down" as soon as the user stop flicking it, just as if the wheel was made out of a heavy piece of metal, spinning freely in bearing. I see, so it makes sense that the spinning ...

Is this something new in macOS 11 (a regression)? I really can't remember now. If you move the wheel on the opposite direction (even if only slightly) or press a button, the dynamic scroll should stop. Yes I know, but Smart scroll should stop when a page or a document ends too, I mean, when the inf...

Not sure I follow. Are you referring to sudden move to the top? That might be what's expected if you flick the wheel (which will active Smart Scrolling). It's about moving away from the window where I triggered Smart scroll, the Smart scroll keeps scrolling: - I (smart) scroll the safari window-web...

This is the issue I was referring to time ago. It happens in Safari and it's Smart scroll related. https://drive.google.com/file/d/1xTEM5obbms78v1HbFoFsSEwVcyTrlybP/view?usp=sharing - one side note about Smart scroll: I tried to use the CMW on an iPad, it works really well, except for the scrolling....

Something strange happens in Safari:
When I have many tabs opened and I scroll (with the wheel) through them, as soon as I move the cursor on the webpage that's opened under the tabs bar, the previous wheel scrolling is performed on the webpage. This doesn't happens if smart scroll is disabled.

ngomes wrote: ↑Wed Feb 24, 2021 11:49 am We have more details on issue WIN-288.

We don't know why causes this problem and we believe only Apple can resolve it.

Sounds very bad in terms of timing resolution. Could you try to engage with Apple devs? Or could it be a CMW firmware glitch?