Ticket #4372 - SpaceBall rotation stops when focus leaves main display panel in v0.18/0.19

[glabifrons]

Does anyone know if there is now a setting for the SpaceBall to only function when focus is on the display panel?
If so, do you know how to revert to the 0.17 (and prior) behavior? I couldn't find any relevant settings in the parameter editor.

As soon as you click into any other panel (or menu), you lose the ability to rotate using a SpaceBall. It works fine again once you click back in the display panel (such as on the model).
For example, if you click on the measure tool, you can no longer rotate the part. If you click on the display panel to regain focus, you exit the measure tool. Being able to rotate when the measure tool is active is extremely handy, when measuring through a part or across something that blocks your view of both surfaces/edges that you wish to use for the measurement endpoints.
There are other uses too, such as rotating as you're making adjustments to properties (such as in Combo View).

[simplemind]

Oh my. I'll have to try this in 0.18 and see.

Yes, I love my SpaceMouse very much. It's a must-have for any CAD software because it saves the right hand to do more productive work and the left hand with SpaceMouse rotates things smoothly.

Rotating while measuring is a must-have as well.

[DeepSOIC]

Does it depend on what navigation style you pick?

[glabifrons]

I'm not sure why it wasn't working before, but measuring doesn't stop the spaceball from rotating (I swear it was when I tested before).
However, clicking in any of the panels still does stop rotation.
I tested with the Combo View panel with all navigation styles, then with Blender selected, I tried the Tree View, Property View, Selection View, Report view, and Python console - all stop rotation using the spaceball.

I double-checked with 0.17 and you can click anywhere within the application (such as editing a property) and still rotate the object (changing focus to another application does stop rotation, as expected).

Sorry for the confusion.

[Boneshaker]

Could confirm this behaviour for Spacemouse

0.16 + 0.17 Spacemouse works anytime

0.18 + 0.19 Py2 Qt4 + 0.19 Py3 Qt5 Spacemouse stops working at any click into the panels, resume at click into 3D view

OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.16784 (Git)
Build type: Release
Branch: master
Hash: ec5720d51c54e6c433cacf207e773aad09dbb25c
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)

[Brutha]

Yes, same behaviour for me with self compiled version as per Vectronic instructions: once you click into e.g. the project window, the space navigator stops responding.

Code: Select all

OS: macOS 10.14
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.16110 (Git)
Build type: Release
Branch: (HEAD detached at 0.18.1)
Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
Python version: 3.7.3
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedKingdom (en_GB)

[glabifrons]

The email confirmation issue for the tracker appears to be fixed, so I was finally able to confirm my account (a bug still exists in that it was never purged, as the initial message indicated would happen without confirmation).

I created a bug report to go along with this issue.
https://tracker.freecadweb.org/view.php?id=4372

Edit: Thanks to whoever quietly fixed the tracker issue!

[M4x]

I can confirm this behaviour with 0/19 u der Ubuntu Linux (I've to post my FreeCAD info later, because I'm in my phone right now).

edit:
I'd like to add that it would make me very happy if FreeCAD would behave differently again!

edit 2:
OS: Ubuntu 20.04 LTS (ubuntu:GNOME/ubuntu)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.21514 (Git) AppImage
Build type: Release
Branch: master
Hash: 89ddab33f692a9bd739171689f9ab0eb58d64b35
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United States (en_US)

[Kunda1]

Updated issue #4372 to Confirmed and made it a target for 0.19 release

[Kunda1]

Anyone willing to work on this fix for the 0.19 release?