Default Keymap Update: Support Fallback tools with RMB Selection #83690

Closed
opened 2020-12-12 04:56:14 +01:00 by Campbell Barton · 7 comments

The fallback tool is the functionality that allows the non-active selection tools to be accessible when LMB-Select is enabled.

Currently this does nothing when RMB select is enabled.

Proposal

For RMB-Select, RMB should activate the fallback tool.

Open Topics

  • The "Active tool" fallback tool doesn't make sense (as it's already accessed via LMB) in this case.
Possible solutions:
  • We could remove the option in this case.
  • Or this item could ignore the tool (keeping the current behavior of always tweaking, ignoring the current selection tool).
The fallback tool is the functionality that allows the non-active selection tools to be accessible when LMB-Select is enabled. Currently this does nothing when RMB select is enabled. ### Proposal For RMB-Select, RMB should activate the fallback tool. ### Open Topics - The "Active tool" fallback tool doesn't make sense (as it's already accessed via LMB) in this case. ``` Possible solutions: ``` - We could remove the option in this case. - Or this item could ignore the tool (keeping the current behavior of always tweaking, ignoring the current selection tool).
Author
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar
Member

After some more discussion this will need to get a more fully fleshed out design task for this. If the Fallback Tools get added to the RCS keymap by mapping them to RMB then this opens quite a few UI questions.
The "Active Tool" option would ideally be disabled or removed.
Tools that previously didn't have Fallback Actions in their UI since LMB was already fully used would now need them (Cursor Tool, Tweak Tool & Annotate Tool).
I would exclude most selection tools from having this feature since these Tools are not really targeted towards RCS users if the Fallback Actions are fully supported.

It is also still very important that the traditional modal operator workflow is not hurt by this inclusion. Right now if RCS users don't want to use the tool they can make sure the Cursor Tool is active, hide the Toolbar and don't have to interact with them anymore.
If the Cursor Tool has Fallback Actions then this is another step that those users need to be aware of if they open someone else's file.
This could be solved with a preference to override those options on file load but that should be further discussed.

After some more discussion this will need to get a more fully fleshed out design task for this. If the Fallback Tools get added to the RCS keymap by mapping them to RMB then this opens quite a few UI questions. The "Active Tool" option would ideally be disabled or removed. Tools that previously didn't have Fallback Actions in their UI since LMB was already fully used would now need them (Cursor Tool, Tweak Tool & Annotate Tool). I would exclude most selection tools from having this feature since these Tools are not really targeted towards RCS users if the Fallback Actions are fully supported. It is also still very important that the traditional modal operator workflow is not hurt by this inclusion. Right now if RCS users don't want to use the tool they can make sure the Cursor Tool is active, hide the Toolbar and don't have to interact with them anymore. If the Cursor Tool has Fallback Actions then this is another step that those users need to be aware of if they open someone else's file. This could be solved with a preference to override those options on file load but that should be further discussed.
Contributor

Added subscriber: @RedMser

Added subscriber: @RedMser
Member

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez

This issue was referenced by c9d9bfa84a

This issue was referenced by c9d9bfa84ad5cb985e3feccffa702b2f3cc2adf8
Author
Owner

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

Changed status from 'Needs Triage' to: 'Resolved'
Campbell Barton self-assigned this 2021-09-21 10:25:53 +02:00
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
5 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#83690
No description provided.