Page MenuHome

frame all shortcut in node editor doesn't work
Closed, ArchivedPublic

Description

System Information
MacBook Pro (Retina, 15-inch, Early 2013)
Graphics card: NVIDIA GeForce GT 650M 1 GB

Blender Version
Broken: version: 2.91, branch: master, commit date: 2020-11-25 08:34, hash: rB0f45cab862b8
Worked: (newest version of Blender that worked as expected)

Short description of error
frame all command in node editor works fine, but any shortcut you assign to it doesn't works

Exact steps for others to reproduce the error

Go to node editor
press Assign Shorcut on view menu to "frame all"
try to use this shortcut

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Aug 4 2021, 12:01 AM

Can't reproduce this issue. I assigned Ctrl+Shift+Alt+A and it works.

Does this happen when you click on File > Defaults > Load Factory Settings?

Maybe that shortcut already assigned?
Did you try to search in "preferences - keymap" by Key-Binding field?

With factory settings it works. But if it is a shortcut conflict is super weird, because I try different ones and no one of them works

@jordi torres (jordi_torres) does Ctrl+Shift+Alt+A work without factory settings?
Do you use default keymap? If so is it modified by you? What @Eugene Du (APEC) suggested is good idea to check, but I would expect you to notice that it does something different.

Can you click on Help > Save System Info and upload saved file? Perhaps some addon is interfering with events, would be good idea to check.

Hi Richard, yes I'm using a custom keymap. This is issue is relative to keymap for sure. Using factory settings serves, but when I switch to my custom keymap, the problem remains. Uploading system info for you to check

Even with custom keymap (copy of default I can't reproduce the issue) Can you upload your keymap here?

Sure, here there is

Richard Antalik (ISS) closed this task as Archived.Aug 7 2021, 3:58 AM

Thanks for keymap file.

Issue here is, that operator does actually run, but the way this works is a bit convoluted - it sets target area to frame and then creates event loop, in order to make this transition smoothly. This event loop uses keymap to catch the event, process it correctly and fire another event or finish the loop.

This is done with view2d.smoothview operator that you have disabled in your keymap. Even such core functionality is visible and I think, that we don't have any means to hide it.

Closing, since this is technically working as expected.

Thanks a lot for your patience. That's working. Some times I disable some commands for to have only the essential ones in my costum keymap. So thanks again