Open Licini opened 10 months ago
For the profile (setting), my current ideal is:
.json
file. keeping its readability and spreadability. This also allows users to build task-specific settings.Rhino
as an ideal reference, Rhino's options
panel provides as many options as possible. Not only keyboard
, but others like Files
, Appearance
, etc. Keyboard
will be our 1st step, but we should keep in mind that the seats should be preserved for them, and they should be added in future rolling versions.
settings.json
and make it hard to read. A setup assistant
(a widget-based visual .json modifier) can be developed to help low-level users create their preferred settings. The underlying architecture can be very much like the MoveIt setup assistant
.
Add an kwarg to App initiation for different mouse and keyboard map for 3D interaction:
Rhino Blender Maya etc.
@ZacZhangzhuo