Object Mode/Workspace Design Conventions #55246

New Issue

Campbell Barton · 2018-05-29T12:56:55+02:00

Campbell Barton commented

2018-05-29 12:56:55 +02:00

This design document outlines our plan for object mode handling.

Object Mode Design

Object mode is per-workspace
(from the user perspective).
When in a mode, selecting objects never changes the mode.
The outliner can move objects in/out of a mode.

(we may have other ways of handling this too - menu, key bindings etc).
When switching modes (besides object-mode), all objects in the current mode

will also change to the new mode.

When switching modes from object-mode, the selection is used, where all objects that match the active objects type will also enter the newly selected mode.
By convention, toggling objects in/out of a mode,

will also set it's selection.

This way manually going to object mode, then into another mode - will use the same set of objects.

When "in a mode" you can't

change to a different mode from the ouliner.

Implications

The selection and object mode are only coupled by-convention - just as you can have active-deselected, it will be possible to have unselected objects in the current workspaces mode.
When in pose mode, it will not be possible to select other armatures where were not explicitly added to pose mode.
There will be cases when you load a file, where the workspace has a mode set, but no objects happen to be in that mode (load without UI for example).

In this case the user will need to add objects to the mode via the outliner for eg.

This is functionally equivilant to loading a file with no objects in 2.79 - where you are still in object mode, it just so happens that you don't yet have anything to operate on.

Notes

Pose + weight paint mode may need special handling, for now we can keep it working as it did in 2.79.
While selection will mostly match the objects in a mode, this isn't something we can guarantee, since switching between view layers, active scenes, py scripts etc.. may set the selection and not change the mode.

This design document outlines our plan for object mode handling. # Object Mode Design - Object mode is per-workspace *(from the user perspective).* - When in a mode, selecting objects **never** changes the mode. - The outliner can move objects in/out of a mode. *(we may have other ways of handling this too - menu, key bindings etc).* - When switching modes (besides object-mode), all objects in the current mode ``` will also change to the new mode. ``` - When switching modes from object-mode, the selection is used, where all objects that match the active objects type will also enter the newly selected mode. - By convention, toggling objects in/out of a mode, ``` will also set it's selection. ``` *This way manually going to object mode, then into another mode - will use the same set of objects.* - When "in a mode" you can't ``` change to a different mode from the ouliner. ``` # Implications - The selection and object mode are only coupled *by-convention* - just as you can have active-deselected, it will be possible to have unselected objects in the current workspaces mode. - When in pose mode, it will not be possible to select other armatures where were not explicitly added to pose mode. - There will be cases when you load a file, where the workspace has a mode set, but no objects happen to be in that mode (load without UI for example). ``` In this case the user will need to add objects to the mode via the outliner for eg. ``` ``` This is functionally equivilant to loading a file with no objects in 2.79 - where you are still in object mode, it just so happens that you don't yet have anything to operate on. ``` # Notes - Pose + weight paint mode may need special handling, for now we can keep it working as it did in 2.79. - While selection will mostly match the objects in a mode, this isn't something we can guarantee, since switching between view layers, active scenes, py scripts etc.. may set the selection and not change the mode.

Campbell Barton commented

2018-05-29 12:56:55 +02:00

Added subscribers: @ideasman42, @dfelinto

Campbell Barton self-assigned this 2018-05-29 12:57:03 +02:00

Joshua Leung commented

2018-05-30 12:50:37 +02:00

Added subscriber: @JoshuaLeung