Make w (context menu shortcut) consistent and independent on what preference for Select is set - Left or Right. w should trigger context menu always. #59045

Closed
opened 2018-12-08 21:43:42 +01:00 by Reinis Adovics · 14 comments

System Information
Operating system: macOS 10.13.6 (17G65)

Blender Version
Broken: 2.80, blender-2.80.0-git20181204.1b6a394d862-x86_64, blender2.8, 2018-12-04

Short description of error
Keyboard shortcuts differ based on what preferences for select is set - left/right.
Expected that whatever mouse selection is preferred, keyboard shortcuts work identically.

Exact steps for others to reproduce the error

Launch Blender.
Add plane.
Tab into edit mode.
Select all mesh.

Set Blender preferences to select with Right mouse button.
Press key "w" for pop-up menu (in 2.8 called Mesh Context Menu, in previous versions it was called Specials).
Menu appears.

Set Blender preferences to select with Left mouse button.
Press key "w" for pop-up menu.
Mesh context menu does not appear. "w" cycles through select modes (Select, Select Box, Select Circle, Select Lasso).

**System Information** Operating system: macOS 10.13.6 (17G65) **Blender Version** Broken: 2.80, blender-2.80.0-git20181204.1b6a394d862-x86_64, blender2.8, 2018-12-04 **Short description of error** Keyboard shortcuts differ based on what preferences for select is set - left/right. Expected that whatever mouse selection is preferred, keyboard shortcuts work identically. **Exact steps for others to reproduce the error** Launch Blender. Add plane. Tab into edit mode. Select all mesh. Set Blender preferences to select with Right mouse button. Press key "w" for pop-up menu (in 2.8 called *Mesh Context Menu*, in previous versions it was called *Specials*). Menu appears. Set Blender preferences to select with Left mouse button. Press key "w" for pop-up menu. Mesh context menu does not appear. "w" cycles through select modes (*Select, Select Box, Select Circle, Select Lasso*).
Author

Added subscriber: @kroko-1

Added subscriber: @kroko-1

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
William Reynish self-assigned this 2018-12-08 22:38:39 +01:00

Don't see a bug here.

Don't see a bug here.
Author

IMHO it is unexpected behaviour as user simply changed mouse related parameter in preferences. It also applies to Object mode where "w" behaves totally different based on left/right setting.
For consistency purposes wouldn't it be the best practice that the same key (keyboard shortcut) does the same thing whatever pointer selection - left or right - method user chooses? And pointer selection preference affects only pointed related stuff?
Same key (shortcut) sure can have different meaning in different Blender editor type. But if different meaning just based on pointer select preference is not a bug... is it not at least bad practice to introduce in 2.8+ Blender where pointer selection option is a "big thing" and you will have newcomers and those who stay with right click having different base shortcuts OOB?
Practically - say there is a team of blenderists each having different pointer selection method in preferences and general knowledge of the software. A newbie asks - how can I subdivide the mesh in Edit mode. The answer is inconsistent.

IMHO it is unexpected behaviour as user simply changed mouse related parameter in preferences. It also applies to Object mode where "w" behaves totally different based on left/right setting. For consistency purposes wouldn't it be the best practice that the same key (keyboard shortcut) does the same thing whatever pointer selection - left or right - method user chooses? And pointer selection preference affects only pointed related stuff? Same key (shortcut) sure can have different meaning in different Blender editor type. But if different meaning just based on pointer select preference is not a bug... is it not at least bad practice to introduce in 2.8+ Blender where pointer selection option is a "big thing" and you will have newcomers and those who stay with right click having different base shortcuts OOB? Practically - say there is a team of blenderists each having different pointer selection method in preferences and general knowledge of the software. A newbie asks - how can I subdivide the mesh in Edit mode. The answer is inconsistent.

We cannot use right click menus when using right click select. That's not possible.

When using right click select, this feature is available by tapping W instead.

We cannot use right click menus when using right click select. That's not possible. When using right click select, this feature is available by tapping W instead.
Author

Sure, no right click contextual menus when having right click as select.
But that is not my argument.
When using Left click why "w" still cannot behave same as when using Right click? In both cases "w" means the same thing (in this discussion it is contextual menu).

Sure, no right click contextual menus when having right click as select. But that is not my argument. When using Left click why "w" still cannot behave same as when using Right click? In both cases "w" means the same thing (in this discussion it is contextual menu).
Author

Another argument apart from consistency to keep "w" as keyboard shortcut to bring out the contextual menu (whatever the click to select option is chosen by the user) is to keep blenderish way of doing things - action can be started and ended by keyboard only, which is faster.
For example we take the same Subdivide which should be achieved by "w s" independently of mouse preferences.
Would you please reconsider this issue?

EDIT:
Updated title of the ticket to more precisely address the issue. I really hope you would reconsider reopening this ticket for discussion.

Another argument apart from consistency to keep "w" as keyboard shortcut to bring out the contextual menu (whatever the click to select option is chosen by the user) is to keep blenderish way of doing things - action can be started and ended by keyboard only, which is faster. For example we take the same *Subdivide* which should be achieved by "w s" independently of mouse preferences. Would you please reconsider this issue? EDIT: Updated title of the ticket to more precisely address the issue. I really hope you would reconsider reopening this ticket for discussion.
Reinis Adovics changed title from Keyboard shortcuts differ based on what preference for Select is set - Left or Right. to Make w (context menu shortcut) consistent and independent on what preference for Select is set - Left or Right. w should trigger context menu always. 2018-12-09 14:22:20 +01:00
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Not a bug. Post suggestions in places such as rightclickselect or devtalk.

Not a bug. Post suggestions in places such as rightclickselect or devtalk.
Author
Looking at @WilliamReynish profile history of how he closes tasks (https://developer.blender.org/T58312) I reopened it to get opinion from another reviser. EDIT Posted in https://devtalk.blender.org/t/keyboard-shortcut-consistency-w-and-independence-on-select-style-left-or-right-forwarded-from-developer-ticket/4245 as diected by @WilliamReynish

Added subscriber: @jeacom

Added subscriber: @jeacom

How many times I see this happening.
I kinda agree with @kroko-1 W should activate context menu both in Left and Right keymaps, there's not a relevant point on making this seemingly random distinction between keymaps. It only makes harder for users who learn different keymaps to talk about the same thing.

How many times I see this happening. I kinda agree with @kroko-1 W should activate context menu both in Left and Right keymaps, there's not a relevant point on making this seemingly random distinction between keymaps. It only makes harder for users who learn different keymaps to talk about the same thing.
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#59045
No description provided.