Transfer Mode operator shortcut #87722

Closed
opened 2021-04-22 19:15:38 +02:00 by Julien Kaspar · 7 comments
Member

This is an accumulation of related tasks and notes on the issues and possible approaches for the shortcut D for the transfer mode operator.
The intention for this is to explore alternative solutions for Blender 3.0. If no solution can be found it will stay on teh current shortcut.

The current solution

After a lot of discussion on this we landed on setting the shortcut on D (release) by default.
This has the advantage of not causing any direct conflict and is universally accessible for any mode & object type.
So this way the operator can grow into a very accessible, commonly used addition to everyone workflow.

A known issue with this is that Annotate is also on D, but instead as a modifier key. This means if a user is holding D to annotate, changes their mind and let's go of D, it will likely cause an accidental switch between objects. (#85538)

Ton also voiced his dissatisfaction with the shortcut choice. His suggestion was to tie it closer to selecting objects.

Transfer Mode via Selecting other Objects

If the toggle for "Lock Object Modes" is disabled in the Topbar -> Edit it will allow users to select and switch between object while in any mode.
Theoretically the transfer mode operator could become a part of this since its functionality is very similar.
The workflow and existing shortcuts for this are inconsistent based on the keymap and modes. So it is impossible to add another shortcut and instead needs a redesign in these shortcuts (Ideally without causing harm to existing workflows).

Current State

1: Select = Set another object as active by selecting the surface
2: Alt + Select = Set another object as active by selecting the surface (Will open a list menu if multiple objects are availible)
3: Ctrl + Select = Set another object as active by selecting the origin point
4: Ctrl + Shift + Select = Set another object as active by selecting the origin point (And keep the previous object selected)

This is not working in Edit Mode though. 1,2 & 4 do nothing and 3 only adds another object to the selection (It does not add it to multi-object Edit Mode).
Even when switching objects in the outliner it will actually exit edit mode.

On LCS the shortcuts are also a bit muddled. 3 only works on weight paint mode (Because of a conflict on Ctrl + LC is to invert the brush). 2 works everywhere but not in weight paint mode (because of a conflict with the gradient tool) and 4 works everywhere.
1, 2, 3 & 4 are also not working for particle edit mode in both LCS & RCS.

Proposal

If we want this to be a target we can look closer into this and update the shortcuts to include the transfer mode operator.
But it won't be an easy task.
So it could be for example based on this:
Select = Set another object as active by selecting the surface
Shift + Select = Set another object as active by selecting the origin point (And keep the previous object selected)
Ctrl + Select = Use the Transfer Mode operator (Set another object as active and use the same mode as the previous object)

There also needs to be a drag threshold in place for LCS for any brushes or tools that use these shortcut combination.
Then the object switching can happen on key release to remove any conflicts.
But this will make brushes inconvenient to use, unless the drag threshold behaviour gets improved.

There's also a very likely downside to using selection for object switching: It will happen by accident a lot!
So this route will not be the most popular one.

Point & Tab

Another shortcut I saw as an alternative is to use Tab. Right now tab is always switching to or from Edit Mode.
Instead Tab could be used for the Transfer Mode operator. There just needs to be a discussion if this can become the default behaviour (which is the most ideal outcome) or if it needs to be an option for the keymap preferences.
Either way, with this solution there needs to be an option to switch between the old and new Tab behaviour in the keymap.

Next

We'll conduct more discussions on this and a closer look at how this can be done and what's the best course of action.
Perhaps there are more solutions to this than outlined right now.
If no satisfactory alternative can be found then the operator will stay on the shortcut D.

This is an accumulation of related tasks and notes on the issues and possible approaches for the shortcut D for the transfer mode operator. The intention for this is to explore alternative solutions for Blender 3.0. If no solution can be found it will stay on teh current shortcut. ## The current solution After a lot of discussion on this we landed on setting the shortcut on D (release) by default. This has the advantage of not causing any direct conflict and is universally accessible for any mode & object type. So this way the operator can grow into a very accessible, commonly used addition to everyone workflow. A known issue with this is that Annotate is also on D, but instead as a modifier key. This means if a user is holding D to annotate, changes their mind and let's go of D, it will likely cause an accidental switch between objects. (#85538) Ton also voiced his dissatisfaction with the shortcut choice. His suggestion was to tie it closer to selecting objects. ## Transfer Mode via Selecting other Objects If the toggle for "Lock Object Modes" is disabled in the Topbar -> Edit it will allow users to select and switch between object while in any mode. Theoretically the transfer mode operator could become a part of this since its functionality is very similar. The workflow and existing shortcuts for this are inconsistent based on the keymap and modes. So it is impossible to add another shortcut and instead needs a redesign in these shortcuts (Ideally without causing harm to existing workflows). ### Current State 1: Select = Set another object as active by selecting the surface 2: Alt + Select = Set another object as active by selecting the surface (Will open a list menu if multiple objects are availible) 3: Ctrl + Select = Set another object as active by selecting the origin point 4: Ctrl + Shift + Select = Set another object as active by selecting the origin point (And keep the previous object selected) This is not working in Edit Mode though. 1,2 & 4 do nothing and 3 only adds another object to the selection (It does not add it to multi-object Edit Mode). Even when switching objects in the outliner it will actually exit edit mode. On LCS the shortcuts are also a bit muddled. 3 only works on weight paint mode (Because of a conflict on Ctrl + LC is to invert the brush). 2 works everywhere but not in weight paint mode (because of a conflict with the gradient tool) and 4 works everywhere. 1, 2, 3 & 4 are also not working for particle edit mode in both LCS & RCS. ### Proposal If we want this to be a target we can look closer into this and update the shortcuts to include the transfer mode operator. But it won't be an easy task. So it could be for example based on this: Select = Set another object as active by selecting the surface Shift + Select = Set another object as active by selecting the origin point (And keep the previous object selected) Ctrl + Select = Use the Transfer Mode operator (Set another object as active and use the same mode as the previous object) There also needs to be a drag threshold in place for LCS for any brushes or tools that use these shortcut combination. Then the object switching can happen on key release to remove any conflicts. But this will make brushes inconvenient to use, unless the drag threshold behaviour gets improved. There's also a very likely downside to using selection for object switching: It will happen by accident a lot! So this route will not be the most popular one. ## Point & Tab Another shortcut I saw as an alternative is to use Tab. Right now tab is always switching to or from Edit Mode. Instead Tab could be used for the Transfer Mode operator. There just needs to be a discussion if this can become the default behaviour (which is the most ideal outcome) or if it needs to be an option for the keymap preferences. Either way, with this solution there needs to be an option to switch between the old and new Tab behaviour in the keymap. ## Next We'll conduct more discussions on this and a closer look at how this can be done and what's the best course of action. Perhaps there are more solutions to this than outlined right now. If no satisfactory alternative can be found then the operator will stay on the shortcut D.
Pablo Dobarro was assigned by Julien Kaspar 2021-04-22 19:15:38 +02:00
Author
Member
Added subscribers: @JulienKaspar, @SirPigeonz, @Sychuan, @Wesley-Rossi, @MeshVoid, @dfelinto, @pablovazquez, @PabloDobarro
Member

In a meeting today we discussed the mode switching shortcuts, and having the transfer mode operator be assigned to the key left to 1 (mapping it on a hardware level, so it's consistent in place in different keyboard layouts). Results of the discussion are in #88071.

In a meeting today we discussed the mode switching shortcuts, and having the transfer mode operator be assigned to the key left to `1` (mapping it on a hardware level, so it's consistent in place in different keyboard layouts). Results of the discussion are in #88071.
Author
Member

@PabloDobarro I think it makes sense to close this task since the Alt + Q shortcut shortcut is so far the most reliable solution that doesn't interfer with any other existing shortcuts.
Do you agree?

@PabloDobarro I think it makes sense to close this task since the Alt + Q shortcut shortcut is so far the most reliable solution that doesn't interfer with any other existing shortcuts. Do you agree?
Contributor

Added subscriber: @dupoxy

Added subscriber: @dupoxy
Contributor
@JulienKaspar There is this issue https://developer.blender.org/T90727
Author
Member

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Author
Member

Since the shortcut Alt Q is now used as a solution for Blender 3.0 I am closing this task.

Since the shortcut `Alt Q` is now used as a solution for Blender 3.0 I am closing this task.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#87722
No description provided.