Menu keyboard shortcuts aren't accurate in Designer?

[synaptic]

Wondering if others are seeing this in Designer 1.9.3. Was trying to make some highlighted text larger, and in the Menu: Text: Size: Bigger, it shows ⌘- > (Command-right caret) as the keyboard shortcut that will do that. But on my M1 Mini Big Sur, that doesn't work. I played around with a ton of other possible shortcuts, and finally came across Shift-Command-right caret that makes the font size 0.1 bigger. 

Is that just my weird Mac that does this, or are some of the stated shortcuts in Designer not correct? 

(I'm also familiar with the way to customize any/all menu shortcuts via Sys Pref: Keyboard: Shortcuts, but checking before I change this)

[Old Bruce]

18 minutes ago, synaptic said:

Is that just my weird Mac that does this, or are some of the stated shortcuts in Designer not correct? 

 

I just checked here on Mac OS 10.14.6 and the menu and keyboard shortcuts both show Command + > . If I want to set that it turns into Shift + Command + . (period/full stop/dot) Very weird.

For me the use of Shift + Command + . is required even if the shortcut is the displayed Command + >

So I would say this is weird.

[Gear maker]

20 minutes ago, synaptic said:

Is that just my weird Mac that does this, or are some of the stated shortcuts in Designer not correct? 

This threw me a bit.  I've never tried these shortcuts before.  But playing with it I have come up with what I believe is happening.  To get the > you would need to press the shift and the period.  So to do the Precise Bigger you need to press cmd + opt + shift + period.  Usually the last character is the lower case symbol, but in this case it is the upper requiring the shift also to be pressed.  At least that's how it works on my mac.

[walt.farrell]

1 minute ago, Old Bruce said:

For me the use of Shift + Command + . is required even if the shortcut is the displayed Command + >

So I would say this is weird.

Well, > is a Shift plus a . (on my keyboard, at least) so how are you going to get Command  + > without using Command, Shift, and "." ?

(But this is something I've complained about on the Windows Affinity applications, even for the shortcuts associated with alphabet characters.

Open is shown as Ctrl + O, I think because O is what shows on the keyboard. But it is really Ctrl + o (minuscule) and Ctrl + Shift + o (shown in the shortcuts dialog as Ctrl + Shift + O) is something different.

[Old Bruce]

20 minutes ago, walt.farrell said:

Open is shown as Ctrl + O, I think because O is what shows on the keyboard.

Regarding what is shown on the keyboard I guess that some keyboards other than US English (the only ones I have ever used) have the > on a different key so in that case the actually typed key combination would be different.

Here is one that I find a little odd. I can use Command and the + sign on the number pad of my extended keyboard to zoom in but I can also use the Command and the = key on the top row of the keyboard to zoom in or I can use Command and the Shift key plus the = sign on the top row of the keyboard to zoom in. But I get nought but a system beep if I use Command and the shift and the = key on the number pad. I expect that if I set the Zoom in shortcut to Command and Shift and = to be the shortcut for zoom then Command  and the + sign would not work. Not going to try it though.

Expectations and Conventions and the ever multiplying sets of Standards.

[R C-R]

5 hours ago, Old Bruce said:

But I get nought but a system beep if I use Command and the shift and the = key on the number pad.

My Apple Extended keyboard does not have any secondary characters (like I would expect to get with the shift key) on its number pad's keycaps, so I assume the beep occurs because there are no characters mapped to the shifted version of any of those keys. In fact, I get a system beep with every one of them in combination with CMD & Shift except for CMD Shift 0 (the number zero) & that is because for me it is an assigned keyboard shortcut for zoom to 800%.

As long as I consider shifted vs. non-shifted key-strokes, it all seems to work as I expect it to.