Keyboard shortcut typo for "Select Next Layer" and "Select Previous Layer"

[MarkOates]

The keyboard shortcuts in the Layer menu have "Select Previous Layer" and "Select Next Layer" listed as Command+UP or Command+DOWN. However, the actual working keyboard shortcut is Option+UP and Option+DOWN.

Specifications:

• OS: MacOS Sonoma 14.2.1 (23C71)
• Tiled Version: 1.10.2

[MarkOates]

Hmm, now I'm unable to reproduce the error. With the Layers panel selected, UP and DOWN (with no Command or Option) will change layers. However with any pane selected, neither of the keyboard shortcuts will change the layer.

[bjorn]

Hmm, these shortcuts are Ctrl + PageUp / Ctrl + PageDown by default, which should translate to Cmd + PageUp / Cmd + PageDown on macOS. Maybe the arrow icons are just a bit confusing? You can see the arrows used for Up / Down in the Raise / Lower Layers actions.

[MarkOates]

I see! That is it. The PageUp/PageDown icons are what confused me.

I did not know this, but, it looks like Apple does have symbols specifically for PageUp/PageDown, different from the Up/Down arrows: https://support.apple.com/en-ca/guide/mac-help/cpmh0011/mac

And, the standard arrows are the line symbols, not the triangles. Which is funny, because the symbols on my keyboard are triangles.

[bjorn]

@MarkOates Right, I have no idea why it uses those other arrows for Up / Down and appears to use the Up / Down arrows for PageUp / PageDown. I wonder if it might be an issue in Qt. On the other hand, this is a native macOS menu, and it does highlight the menu when those keys are pressed, so it might also be an inconsistency in macOS. 🤷‍♂️

[MarkOates]

OK, I did a quick skim online and across a few different applications on my Mac and I wasn't able to find any active Qt issues or mentions of it, or even another application on my Mac that had the PageUp or PageDown icon to cross-reference.

Enough cost/payoff digging for me! I'm happy to close the issue if you like. Thanks. :)

[bjorn]

@MarkOates Thanks for doing some digging! I also had a quick look but could not find anything either. It does seem like a valid issue, so I'll keep it open for later.