Page MenuHome

Keymaps for Nodes Selection in node graphs can't be customized
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: AMD Radeon (TM) R9 380 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: rBb292cfe5a936

Short description of error
I was trying to change the keymap for selecting nodes in the node graphs.
The default being: LMB for selection and Shift + LMB for selection extension.

In the screen capture below, all of these keys do nothing when changed, disabled, or deleted. The default selection remains the same as the default described above.
Is this selection behavior hard coded (and the keys have become vestigial)?

Exact steps for others to reproduce the error

  1. Go to Edit > Preferences > Keymap > Node Editor > Node Editor (Global)
  2. Try to affect one of the keys framed in the screenshot above (example: try to change Extend selection (Shift + LMB) for Ctrl + LMB)
  3. In any of the node graphs, the selection remains Shift + LMB

Event Timeline

Omar Emara (OmarSquircleArt) changed the task status from Needs Triage to Needs Information from User.Nov 11 2022, 11:45 AM

That's probably because the selection tools shortcuts are still active. You would need to adjust all of those as well. Try deleting all of those and you will see that selection is no longer possible. Does this work as expected?

@Omar Emara (OmarSquircleArt)
This worked indeed, but now the problem is that these seem to not be indexed in the keymap under : Keymap > Node Editor > Node Editor (Global).
I could only find them via the filter search…

Is there any plans to show them in the keymap?
And what is the reason for having them in double?

Omar Emara (OmarSquircleArt) changed the task status from Needs Information from User to Needs Information from Developers.Nov 11 2022, 2:07 PM

I am not sure why those keymap entries are not visible, or if it is intended. Will tag the module for more information.

Actually, it would be best if you can open a separate report for this one, can you do that?