Node Wrangler : Shortcuts don't work on Mac #70296

New Issue

PHILIPPE RAMEAUX · 2019-09-27T11:50:15+02:00

PHILIPPE RAMEAUX commented

2019-09-27 11:50:15 +02:00

System Information
Operating system: Mac 10.14.6 Mojave
Graphics card: AMD RX 580 Pulse (not compatible with Cycles)

Blender Version
2.80 2019-07-29,

Short description of error

Shortcuts don't work in the Shading Space

Exact steps for others to reproduce the error

**System Information** Operating system: Mac 10.14.6 Mojave Graphics card: AMD RX 580 Pulse (not compatible with Cycles) **Blender Version** 2.80 2019-07-29, **Short description of error** Shortcuts don't work in the Shading Space **Exact steps for others to reproduce the error**

PHILIPPE RAMEAUX commented

2019-09-27 11:50:15 +02:00

Added subscriber: @philippe90

Philipp Oeser commented

2019-09-27 13:56:04 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-09-27 13:56:04 +02:00

Please also try with the latest build from http://builder.blender.org.

If that doesnt solve the issue, please be more specific in regards to which shortcuts are not working... All of them?

Please also try with the latest build from http://builder.blender.org. If that doesnt solve the issue, please be more specific in regards to which shortcuts are not working... All of them?

PHILIPPE RAMEAUX commented

2019-09-27 14:38:46 +02:00

All of them!

CTRL + T,
CTRL+SHIFT+T
CTRL+0
CTRL +SHIFT+left clic
etc.

Same thing with 2.81 version

Could it be a conflict (or something to see) with Mac shortcuts. I've noticed that F12 to Render doesn't work because it's the sound volume on the keyboard. But Node Wrangler shortcuts are not Mac shortcuts.

All of them! CTRL + T, CTRL+SHIFT+T CTRL+0 CTRL +SHIFT+left clic etc. Same thing with 2.81 version Could it be a conflict (or something to see) with Mac shortcuts. I've noticed that F12 to Render doesn't work because it's the sound volume on the keyboard. But Node Wrangler shortcuts are not Mac shortcuts.

PHILIPPE RAMEAUX commented

2019-09-27 14:52:27 +02:00

I solved the PB with Keyboard preferences for F12
And I was mistaken with my keyboard touch. So sorry !

I solved the PB with Keyboard preferences for F12 And I was mistaken with my keyboard touch. So sorry !

Philipp Oeser commented

2019-09-27 15:03:39 +02:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2019-09-27 15:03:39 +02:00

Philipp Oeser self-assigned this 2019-09-27 15:03:39 +02:00

Philipp Oeser commented

2019-09-27 15:03:39 +02:00

Thx for getting back, I assume this can be closed then?
(feel free to comment again if issues persist...)

Thx for getting back, I assume this can be closed then? (feel free to comment again if issues persist...)

PHILIPPE RAMEAUX commented

2019-09-27 16:25:46 +02:00

Thx for help. Topic can be closed

Julian commented

2019-12-23 23:24:09 +01:00

Added subscriber: @joolian.4bes

Julian commented

2019-12-23 23:24:09 +01:00

In #70296#784767, @philippe90 wrote:
I solved the PB with Keyboard preferences for F12
And I was mistaken with my keyboard touch. So sorry !

Hi there! Could you please elaborate on how you fixed this issue.

I am currently using a Windows Keyboard which is plugged into my Mac, however the CNTRL key has been assigned the CMD key function from Mac. Not sure if this is relevant as the Node Wrangler commands do not work when using the native Mac Keyboard either....

Any help would be greatly appreciated!

> In #70296#784767, @philippe90 wrote: > I solved the PB with Keyboard preferences for F12 > And I was mistaken with my keyboard touch. So sorry ! Hi there! Could you please elaborate on how you fixed this issue. I am currently using a Windows Keyboard which is plugged into my Mac, however the CNTRL key has been assigned the CMD key function from Mac. Not sure if this is relevant as the Node Wrangler commands do not work when using the native Mac Keyboard either.... Any help would be greatly appreciated!

Nathaniel commented

2020-07-11 08:52:59 +02:00

Added subscriber: @Nathaniel-6

Nathaniel commented

2020-07-11 08:52:59 +02:00

Hi, sorry, could someone explain how to make these shortcuts work? It's great that the OP was able to solve the problem for themself, but I have literally no idea what "I solved the PB with Keyboard preferences for F12" could mean.

Nathaniel commented

2020-07-11 09:02:18 +02:00

Oh, I think I figured it out. It's not an OS X issue, it's just that, like most things in Blender, Node Wrangler has invented its own inexplicable and completely unguessable user interface convention for no reason. You don't ctrl-shift-click on the port you're trying to preview, you ctrl-shift-click on the node, i.e. the box that the ports are attached to. Ctrl-shift-click cycles through the different ports.

(Also note that it is ctrl-shift-click on the Mac and not CMD-shift-click as you might expect.)

Oh, I think I figured it out. It's not an OS X issue, it's just that, like most things in Blender, Node Wrangler has invented its own inexplicable and completely unguessable user interface convention for no reason. You don't ctrl-shift-click on the *port* you're trying to preview, you ctrl-shift-click on the *node*, i.e. the box that the ports are attached to. Ctrl-shift-click cycles through the different ports. (Also note that it is ctrl-shift-click on the Mac and not CMD-shift-click as you might expect.)

Sign in to join this conversation.