Keymap conflict (Node Editor / Node Wrangler) #65202
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#65202
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.17134 64 Bits
Graphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71
Blender Version
Broken: version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-26 22:34, hash:
blender/blender@d525c76003
Worked: (optional)
Short description of error
With the default keymap, Shift+RMB and drag on a connection on the Node Editor creates a reroute node, and Ctrl+RMB drag cuts the connections... but if Node Wrangler addon is enabled, Ctrl+RMB drag enables the "Lazy connect" option of Node Wrangler, overwriting the connection cutting shortcut. I understand that it's an addon, but being that it comes bundled in Blender and given that it's arguably necessary to get the most out of the Node Editor, it shouldn't create conflicts like this.
Exact steps for others to reproduce the error
Works in any file. Just try to cut connections between nodes using Ctrl+RMB drag with Node Wrangler addon enabled.
Thanks!
Added subscriber: @OliverVillar
#66700 was marked as duplicate of this issue
blender/blender#66341 was marked as duplicate of this issue
Added subscribers: @WilliamReynish, @lichtwerk
@WilliamReynish : I am a bit on shaky ground when it comes to keymap convention: why are we having reroute/cut swapped from LMB to RMB (when choosing
Select with
Left
in keymap preferences)?in 2.79 it was always LMB (no matter what was chosen for
Select with
...)Just asking here to see if NodeWrangler should also do some keymap swapping [LMB <-> RMB] depending on
Select with
User Preference.@lichtwerk Well, Ctrl-LMB and Shift-LMB are use to add and remove for box select, so they are already used. Same in other editors, which is why setting the 3D Cursor in the 3D view is done with Shift-RMB.
Added subscriber: @BrendonMurphy
hi, with addons overwriting built in key maps usually they provide same functionality, extended functionality or pie v's standard menu. They should where possible not overwrite built in functions. The simple solution in this case would be to remap the offending keymap conflict/s in the addon.
@lichtwerk as the default is now left click select, it's all that's required by the addon. To work with the defaults. That said, if there was a module that addons could call that generically swaps "left to right" it would be handy for old timers that still wish to use right mouse select?
@WilliamReynish : ok, I see (sort of -- I am RMB selector....we dont have LMB box in the node editor... except for the box-tool, then reroute/cut is not functional which is expected...)
having this swapping generic would be nice. for this report: should we just go over shortcuts and swap depending on preference?
Yes that should work. Maybe the offending key could be moved to alt shift?
Added subscriber: @AlexBitsadze
Added subscriber: @billyand
Is this supposed to be assigned to someone or is this just not that much of a problem?
hi, assigned to Philipp, We all know about this issue.
Changing priority to high. We need to make a decision and make a move on this before rc1.
Hesitating to just commit something here, but here is what I would do:
Default keymap current state
Alt
RMB
freeCtrl
RMB
cut linksCtrl
Shift
RMB
freeNodeWrangler current state
Alt
RMB
Lazy mixCtrl
RMB
Lazy Connect (offending)Ctrl
Shift
RMB
Lazy Connect menuNodeWrangler proposed future
Alt
RMB
Lazy ConnectAlt
Shift
RMB
Lazy Connect menuCtrl
Shift
RMB
Lazy mixThis keeps the two
Lazy Connect
on a common "base" key and movesLazy mix
... Does this sound OK?Added subscriber: @brecht
Sounds good to me.
Seems reasonable
Added subscriber: @SeanKennedy
Is there a way for cut links to go back to ctrl LMB? Right now LMB and Ctrl LMB both do box select
@billyand : LMB is select [Deselect on nothing ON], Ctrl LMB is select [Deselect on nothing OFF] (which is like toggle), so these are not the same...
Guess I will commit the above now...
This issue was referenced by
e08d6983c0
Changed status from 'Open' to: 'Resolved'
Added subscriber: @Damjan-2