[2.0.39] Inconsistent behavior for switch to surface shortcut

[arkrusade]

In editor mode, the switch to surface short cut has inconsistent behavior. Sometimes it will switch to a surface when pressing ctrl + 1, sometimes it will just get the quickbar item as if I had only pressed 1

I can consistently get the surface behavior on key up events:
1. press down ctrl
2. press down 1
3. press down 2
4. release 1

1. press down ctrl
2. press down 1
3. press down 2
4. release 2

step 4 consistently switches surfaces, all other key events go to quickbar instead

P.S. would love to have this as a shortcut in normal play too.

[Rseding91]

Thanks for the report however I'm not seeing any bug here. The shortcut will activate if the required keys are all active at the same time, and other keys are not. If the quickbar is activating it means the ctrl key is not being held down (you released it early, or pressed the number key before ctrl).

[arkrusade]

The ctrl key is being held down, for me anyway. In the steps I described, I never release the ctrl key.

So I'm pressing ctrl + 1 or ctrl + 2 and not switching surfaces, but getting quickbar instead. So the quickbar is activating even though I'm pressing the keyboard shortcut for surfaces instead.

Bug behavior

1. Press control key
2. Press 1

Results: Quickbar activates


Expected behavior

1. Press control key
2. Press 1

Results: switch to surface (nauvis)

[Rseding91]

Ah, I see the confusion. I always test with ctrl + numpad-#. Since the quickbar hotkey is identical to the editor switch-surface hotkey, one of them gets priority and it happens to be the quickbar version. If I changed it, then someone would likely complain that it's switching surfaces instead of activating the quickbar shortcut.

If you have a numpad, you can use those - since as far as I know there are no hotkeys bound to ctrl + those by default.

[arkrusade]

I see, though I'm not sure why one should get priority since they're different shortcuts.

Since ctrl + top row number has no default, doesn't it make sense to prioritize the ctrl-based shortcut instead of the number-only-based shortcut if ctrl is pressed? There should be no change in behavior for quickbar usage or any other behaviors, unless they have manually changed ctrl + number to be a new shortcut.

If ctrl + number were to get priority, it would only affect those people who manually mapped it. Otherwise, there shouldn't be any complaints since pressing 1 without control should still work as normal.

I'm also curious as to why this is an editor-only shortcut, would love if you could provide some insight into that decision.