Page MenuHome
Paste P559

Workspace mode design task description
ActivePublic

Authored by Julian Eisel (Severin) on Nov 18 2017, 5:38 AM.
= Workspaces: Integrating Interaction Modes
== Motivation
Workspaces are introduced as a key factor for optimizing workflows in 2.8. With them, it should be possible to change tasks requiring different UI setups easly. Thereby, the interaction mode plays a huge role. It defines the toolset and options available. That means it has to work well together with the workspace.
As an example, when a user enters a workspace for animation, the pose mode should be enabled.
Right now the interaction mode is stored per object.
It also affects the UI of multiple editors (3D View, Properties Editor, UV/Image Editor), so it can't be just a 3D View option.
== Requirements
We need a design that meets the following requirements:
# Workspaces shall be able to affect the interaction mode, so that users don't need to switch it manually when switching workspaces.
# When switching workspaces, the newly activated workspace may be in a mode that the active object does not support. This should be handled nicely.
# It must be possible to switch interaction mode without switching workspace.
# While in weight paint mode, it must be possible to select the bones to paint weights for.
For reference, the current (ugly) workflow is:
* Enter pose mode for armature to draw weights for
* Select object to draw weights on (Blender switches to object mode)
* Switch to Weight Paint Mode
* Now bones from the armature(s) in pose mode can be selected with {key Selectmouse}, painting happens with {key Actionmouse} (may fail if object doesn't have an active vertex group)
# Setting bones as parents for objects should be possible from within the 3D View.
For reference, the current (again ugly) workflow is:
* Select bone in pose mode
* Select object (Blender switches to object mode)
* Select bone again (Blender switches back to pose mode)
* Call operator "Make Parent" ({key Ctrl P})
* Select "Bone"
# Multiple workspaces can be active in parallel by opening multiple windows. That means multiple interaction modes may be active in parallel too which shall work nicely.
# The interaction mode needs to be changeable easily and swiftly.
# Button for the interaction mode needs to be easy to reach in a place that communicates its scope well.
== Proposed Solution
A proposed solution was to make the interaction mode a per workspace option. This is probably the most obvious one and doesn't require major overhauls.
It resolves requirements #1 and #3. For further requirements, we need additional solutions.
** Re Requirement #2
We could store the active object per workspace, meaning changing workspace would also change the active object (and go back to the mode it was before). In the following cases this wouldn't work:
* Opening workspace for the first time after adding/appending. It doesn't have an active object from the current scene then.
* Activating a workspace whose active object has been deleted meanwhile.
We can fall back to object mode then.
** Re Requirement #4
The painting itself can mostly happen like now (paint with {key Actionmouse}, select bones with {key Selectmouse}. We still need a way to decide which armatures can be painted weights for. Some options:
* Bones from all (visible, selectable) armatures can be selected.
* Check Armature Modifiers of an object and only allow selecting bones from armatures set in these.
* Only allow entering Weight Paint Mode with some armature(s) selected.
* Have some UI to enable/disable armatures for weight painting.
* More drastic changes, like redesigning how armatures and mesh-objects work together.
We may have to test some of these options in practice to see which works best.
** Re Requirement #5
TODO
** Re Requirement #6
Should work mostly fine, issues only arise when different modes display the same data but with different internal storage techniques. For example, sculpt mode stores the sculpted mesh in a different structure than other modes. Converting it for other modes may be a heavy operation.
Some options:
* Don't allow having such conflicting modes active in parallel.
* Allow modes to display data from other modes (e.g. edit mode can display sculpt mesh structure) and convert meshes only when needed (e.g. user executes tool in edit mode after having worked in sculpt mode.)
** Re Requirements #7 and #8
Interaction mode of a workspace would be switched either using a hotkey, or using a button in the top-bar. The top-bar clearly indicates that this is an option affecting multiple editors.

Event Timeline