Shift + 1234567890 not working in Edit Mode. #96115

Closed
opened 2022-03-02 02:52:59 +01:00 by Gabriel Gazzán · 21 comments

Hi there!

Apparently shortcuts that use numeric keys (main keyboard) with modifier key SHIFT are not working properly in Edit Mode (at least).
The conflict is the "usual one" of the !@#$%^&*() characters not being taken as SHIFTed versions of 1234567890.

Greetings!
g

Hi there! Apparently shortcuts that use numeric keys (main keyboard) with modifier key SHIFT are not working properly in Edit Mode (at least). The conflict is the "usual one" of the !@#$%^&*() characters not being taken as SHIFTed versions of 1234567890. Greetings! g
Author
Member

Added subscribers: @GabrielGazzan, @mont29

Added subscribers: @GabrielGazzan, @mont29
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Hi, thanks for the report.
Are you using custom keymap or default one?
I can not reproduce at least with Select mode switching (Shift 1-3)

Hi, thanks for the report. Are you using custom keymap or default one? I can not reproduce at least with Select mode switching (Shift 1-3)

Removed subscriber: @mont29

Removed subscriber: @mont29
Author
Member

Thanks for checking it Pratik.
Yes, I'm using default keymap.

I've noticed the problem while trying to use Shift + 5 (Extrude Along Normals shortcut).
Now I've also tried changing its shortcut to be just E (replacing the default Extrude Region shortcut) and, although the change seems to have taken place, when I hit E it activates the Extrude region tool, and not the suposed one.
So it seems to be another kind of issue...

Thanks for checking it Pratik. Yes, I'm using default keymap. I've noticed the problem while trying to use Shift + 5 (Extrude Along Normals shortcut). Now I've also tried changing its shortcut to be just E (replacing the default Extrude Region shortcut) and, although the change seems to have taken place, when I hit E it activates the Extrude region tool, and not the suposed one. So it seems to be another kind of issue...
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Can you provide system information, Blender version, the last Blender version which worked, and the exact steps to reproduce the problem?

It's good to keep in mind that we need to replicate the problem in order to fix it, and the key detection system may vary by operating system and Blender version.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Can you provide system information, Blender version, the last Blender version which worked, and the exact steps to reproduce the problem? It's good to keep in mind that we need to replicate the problem in order to fix it, and the key detection system may vary by operating system and Blender version. A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Author
Member

sorry for not following up in time.
the problem still persists.

PC type: HP Notebook AMD A6-9225
Graphics: RADEON R4
S.O.: WIndows 10
Blender version with issue: 3.1 official release
(last version which worked: I don't really know)

Steps to reproduce:

  1. With the default cube selected, enter Edit Mode.
  2. Select some faces.
  3. Select "Extrude Along Normals" tool. (use it or cancel it)
  4. Right click over the "Extrude Along Normals" icon in the left side toolbar.
  5. Select choose "Assign Shortcut".
  6. Press Shift + E.
  7. Now try to use the new shortcut to activate the "Extrude Along Normals" tool.

Expected behavior: "Extrude Along Normals" is activated.
What actually happens: "Edge Crease"is activated instead.

Note: The same happens for example (as I noted above) if you try to use just "E" as shortcut. In that case, after supposedly changing the shortcut to the new tool, the tool originally assigned to "E" (Extrude Region) is really activated.

sorry for not following up in time. the problem still persists. PC type: HP Notebook AMD A6-9225 Graphics: RADEON R4 S.O.: WIndows 10 Blender version with issue: 3.1 official release (last version which worked: I don't really know) Steps to reproduce: 1. With the default cube selected, enter Edit Mode. 2. Select some faces. 3. Select "Extrude Along Normals" tool. (use it or cancel it) 4. Right click over the "Extrude Along Normals" icon in the left side toolbar. 5. Select choose "Assign Shortcut". 6. Press Shift + E. 7. Now try to use the new shortcut to activate the "Extrude Along Normals" tool. Expected behavior: "Extrude Along Normals" is activated. What actually happens: "Edge Crease"is activated instead. Note: The same happens for example (as I noted above) if you try to use just "E" as shortcut. In that case, after supposedly changing the shortcut to the new tool, the tool originally assigned to "E" (Extrude Region) is really activated.
Author
Member

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

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

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Author
Member

In this part of today's "Blender Hoy" live stream , @pablovazquez just came across this very issue with shortcuts.

He tried to redefine the Shift+A shortcut in the Node Editor to call some other command (Search Node), and although the program seemed to perform the task, when he tried to use the new shortcut, the default command for that key combination (Add Node) was executed instead of the newly assigned one (Search).

In [this part of today's "Blender Hoy" live stream ](https://youtu.be/4khMIEOUjck?t=2973), @pablovazquez just came across this very issue with shortcuts. He tried to redefine the Shift+A shortcut in the Node Editor to call some other command (Search Node), and although the program seemed to perform the task, when he tried to use the new shortcut, the default command for that key combination (Add Node) was executed instead of the newly assigned one (Search).

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

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

I've checked the video and I've seen similar issues mentioned other times.
What happens is a common error due to a shortcut limitation.
If two operators have the same shortcut assigned, the other operator is only executed if the first one allows PASS_THROUGH.
In other words, there is a shortcut conflict and only one operator is executed in the case.
If you want the shortcut to work for the other operator, disable one of then.
Captura de Tela 2022-04-25 às 22.16.31.png

I've checked the video and I've seen similar issues mentioned other times. What happens is a common error due to a shortcut limitation. If two operators have the same shortcut assigned, the other operator is only executed if the first one allows `PASS_THROUGH`. In other words, there is a shortcut conflict and only one operator is executed in the case. If you want the shortcut to work for the other operator, disable one of then. ![Captura de Tela 2022-04-25 às 22.16.31.png](https://archive.blender.org/developer/F13027786/Captura_de_Tela_2022-04-25_a_s_22.16.31.png)
Author
Member

Oh, I see... thanks for checking it.

Perhaps it would be a good idea (from a UX point of view) to issue a warning to the user, when such a case is reached (i.e. when a new assigned shortcut collides with another previously assigned).
That way at least users would know the reason for this apparent "malfunction" and could take action.

Oh, I see... thanks for checking it. Perhaps it would be a good idea (from a UX point of view) to issue a warning to the user, when such a case is reached (i.e. when a new assigned shortcut collides with another previously assigned). That way at least users would know the reason for this apparent "malfunction" and could take action.

It's not that simple.
Multiple operators using the same shortcut is allowed.
Some operators are only activated under specific conditions, when not activated another operator with the same shortcut takes place.
And there are operators that allow PASS_THROUGH, allowing another with the same shortcut to be activated.
These cases are not identifiable.

It's not that simple. Multiple operators using the same shortcut is allowed. Some operators are only activated under specific conditions, when not activated another operator with the same shortcut takes place. And there are operators that allow `PASS_THROUGH`, allowing another with the same shortcut to be activated. These cases are not identifiable.
Author
Member

I understand Germano, thanks for the explanation.

Still, if/when technically feasible, it'd be good if users could get some cue of why a recently added shortcut would not work, although it seemed to be successfully assigned.

Greetings!

I understand Germano, thanks for the explanation. Still, if/when technically feasible, it'd be good if users could get some cue of why a recently added shortcut would not work, although it seemed to be successfully assigned. Greetings!
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
4 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#96115
No description provided.