Hi Chris --

> I would propose Cmd+Shift+] if it is not too difficult for non-US keyboards. 

For clarification, the shift state is already encoded in shortcuts implemented via #keyStroke:'s #keyCharacter. So, cmd+S and cmd+shift+s and cmd+shift+S are essentially all the same thing. Unless there is a keyboard layout out there that has the uppercase S as an extra key.... :-D That's also the reason why it is tricky to create shortcuts that involve characters other than alphabetical ones. A..Z and special characters (space, return, ...) are fine. 0..9 is fine if it is not combined with a shift state because that would, again, be mixed up in all those different keyboard layouts. And even this A...Z is rather specific to "our" Latin-based region. Just think of Asian characters/symbols ... 

Note that we can use some function keys when implementing those shortcuts via #keyDown: as our OSVM does (correctly) not generate keystroke events for those. But one would have to double check, whether, e.g., F9 to F12 actually arrive in the image on macOS, Windows, and X11/Ubuntu/Linux.

Best,
Marcel
Am 29.12.2021 23:29:31 schrieb tim Rowledge <tim at rowledge.org>:


> On 2021-12-29, at 1:12 PM, Chris Muller wrote:
>
> I'm really sorry for my misread! I would propose Cmd+Shift+] if it is not too difficult for non-US keyboards.

I think that is part of the original problem - they're stuck having to type ctl-alt-8 just to get the ]. So cmd-ctl-alt-shift-8 is a bit of a handful...

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Never write software that anthropomorphizes the machine. They hate that.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20211230/e845b6a9/attachment.html>