[profile system] Shared modes across buttons and bindings

[DavidLiu]

JohnHind’s device-button proposal is a useful example of something the current bindings can’t quite express:

Using device buttons rather than keyboard to change Rotatrix modes

Hi David, Continuing my review comments, here is how I think the buttons should be allocated. My use is at present entirely in Fusion, but I think it would be similar in any 3-D application. Everything is at the latest software version. Left rear button (press and release): return to pointer mode, do nothing if already in that mode. Right rear button (press and release): If in pointer mode, switch to orbit mode. Otherwise toggle between orbit mode and pan and zoom mode. The left front button …

The idea is to let a profile define named modes that several bindings can share. For example, Pointer, Orbit, and Pan & Zoom:

• Left rear always selects Pointer, including doing nothing if already there.
• Right rear selects Orbit from Pointer, then alternates between Orbit and Pan & Zoom.
• The modes stay active after releasing the buttons.
• Left front can snap rotation to an axis while in Orbit.

A binding could set a particular mode, cycle through selected modes, or apply only while a given mode is active. Each mode would provide the appropriate ball behavior and axis mapping, with an explicit default mode.