zlacker

[parent] [thread] 3 comments
1. eyelid+(OP)[view] [source] 2021-12-17 07:22:06
You’re totally right that fullscreen breaks cmd ~. It also breaks cmd tab in unexpected ways.

You’re also right about lack of visual feedback, which is disappointing given the various stuff that I think is still currently branded Mission Control, where obviously the fundamentals are already there.

Cmd ~ isn’t statically ordered though, it’s either application specific or based on recent use in a weird (easy to confuse) heuristic. It follows a similar (maybe identical?) pattern to recent use for cmd tab, and even app switching on iOS.

replies(1): >>Propha+vI
2. Propha+vI[view] [source] 2021-12-17 13:24:44
>>eyelid+(OP)
To your third point, is this a setting somewhere? I tested before I posted w/ 4 Brave windows, but they stay in the same order.

Makes sense, since cmd+~ immediately switches on key down to the next window; cmd+tab (like alt+tab in Win) lets you keep the selection open and choose an out-of-order app, which alters the MRU. How would you do that here? The only way I've affected it is creating/killing windows at points in the cycle. Using cmd+shift+~ for me just goes backward in the same static order.

replies(2): >>eyelid+Gn1 >>CRConr+eke
◧◩
3. eyelid+Gn1[view] [source] [discussion] 2021-12-17 16:22:33
>>Propha+vI
Some kind of interaction with the window usually (again can be app specific) … reverses the order to the window where this sequence started, then may or may not continue the original order.

I’ve seen this most consistently in apps where I commonly have too many windows open, VSCode iTerm and Chrome being the worst offenders. Edit: my worst offenders, the apps don’t do anything unusual here.

◧◩
4. CRConr+eke[view] [source] [discussion] 2021-12-22 00:41:46
>>Propha+vI
Chose another window with the mouse to change the MRU order, then test the key combos again?
[go to top]