You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Cuis uses cmd-< and cmd-> to cycle windows. This works (for example) on a Mac with US defaults, where the Finder shortcuts for doing that (cycling the windows of the same app) are cmd-and cmd-shift-. But it doesn't work on a Mac with German defaults, where cmd-< and cmd-> are the Finder (OS) shortcut; because the Squeak VM doesn't get these keystrokes.
What we want is pretty different. We'd like to use the same keystrokes as Finder. We need a way to tell OS-X that we want to handle the "next window in same app" and "previous window in same app" events ourselves, and react to them. Most likely this requires some VM level work.
In addition, think about (and implement) reasonable behaviors for other OSs, like Windows and Linux, that most likely don't have keystrokes for this behavior.
The text was updated successfully, but these errors were encountered:
This has been an issue in Chromium and Firefox, and I believe it is still an issues in Photoshop. As a workaround I implemented option-tab and option-shift-tab to cycle windows on the Mac.
Currently Cuis uses cmd-< and cmd-> to cycle windows. This works (for example) on a Mac with US defaults, where the Finder shortcuts for doing that (cycling the windows of the same app) are cmd-
and cmd-shift-
. But it doesn't work on a Mac with German defaults, where cmd-< and cmd-> are the Finder (OS) shortcut; because the Squeak VM doesn't get these keystrokes.What we want is pretty different. We'd like to use the same keystrokes as Finder. We need a way to tell OS-X that we want to handle the "next window in same app" and "previous window in same app" events ourselves, and react to them. Most likely this requires some VM level work.
In addition, think about (and implement) reasonable behaviors for other OSs, like Windows and Linux, that most likely don't have keystrokes for this behavior.
The text was updated successfully, but these errors were encountered: