Hotkeys conflict between Shader Nodes, Compositing Nodes, GeoNodes and Texture Node Editor. #93403
Labels
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93403
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68
Blender Version
Broken: version: 2.93.6, branch: master, commit date: 2021-11-16 14:54, hash:
c842a90e2f
Worked: (newest version of Blender that worked as expected)
Short description of error
I have hotkeys on frequently used nodes in shader editor. When I switch to Compositing, first of all I have hotkeys already assigned to similar nodes (I did it in shader editor, but they are automatically assigned in compositing). Secondly, I get an error in Compositing - Not a shader or geometry node tree.
Exact steps for others to reproduce the error
You get the following error
https://archive.blender.org/developer/file/12282/12282119/bandicam_2021-11-26_16-53-56-020.mp4
https://archive.blender.org/developer/file/12271/12271877/Node_Conflict.blend
Added subscriber: @Oxicid
Hotkeys conflict between Shader Nodes, Compositing Nodes and Texture Node Editor.to Hotkeys conflict between Shader Nodes, Compositing Nodes, GeoNodes and Texture Node Editor.The following categories should be added to the hotkeys settings, to avoid conflicts between hotkeys
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Hi, thanks for the report. I am not able to reproduce this on master and 2.93.7 (
4ec6cc412d7f
)To reproduce the error. Could you please provide exact reproducing steps? I manually changed the shortcut. Not sure if I understand the use of py script.
Can you reproduce this issue with factory settings?: {nav File > Defaults > Load Factory Settings}
bandicam 2021-11-26 16-53-56-020.mp4
{nav Shading > Ctrl+A > Color > Invert > right mouse button > Assign Shortcut > I}
Now everything will work fine in the shading mode, but in other node editors, when you press "I" you will get an error.
PS. And the .py file is not a script, but saved hotkeys
Changed status from 'Needs User Info' to: 'Confirmed'
Hi, thanks for clarifying. Can confirm now :)
Agree that each of the node editors should have their own set of shortcuts, even if it means duplicating the shortcuts for the nodes that do work across different editors.
i am not able to reproduce the issue , has this been patched already ?
@ravikul-rao I believe contributions to this are still welcome. If you get a chance to work on this remember to refer to this issue, so people following it can help with testing.
Hello! Is anyone working on the problem? I would take it upon myself to solve it.
Hi! I have a solution to the problem, but it seems a bit ugly to me. How can we discuss the code?
@arevkov hi, if you've a PR ready then feel free to submit it: https://wiki.blender.org/wiki/Tools/Pull_Requests
Discussion can happen there.
Alexander Revkov referenced this issue2023-04-13 14:53:39 +02:00
Is the task relevant?
Guys, please don't. It's already borderline impossible to maintain any other than default keymap and this pushes it beyond point. The amount of keymap entries for node editor is already insane, and quadrupling it is beyond insanity. What Blender gravely needs is unification of shortcuts, not going in opposite direction.
@dfelinto I am honestly curious here. What made you conclude that instead of a simple check whether node can be added in given node editor context, the best course of actions would be to add 246 new keymap entries? (Default keymap has currently 82 entries for node editor). I can't imagine you've considered how difficult it already is to make a custom keymap for Blender, and this change would quadruple that difficulty for node editor section.
Especially given that what changes between node editor modes are just the nodes. Here's a very obscure use case of someone having hotkeyed specific nodes. The solution to such obscure use case should not have devastating effect on keymap customization. I really want to know your thought process here.
@Rawalanche In some ways you are right, perhaps we should leave the global keys in place, and only have custom hotkeys displayed in separate tabs.
Now the solution is to write a script yourself, so that it adds this or that node by context.
Existing keymap entries would not be duplicated but stay in a common node editor keymap. There would be additional, initially empty keymaps for custom shortcuts per node type. But that still has design challenges for user keymap editing, as I mentioned in the PR.