[BUG] switch-window-backwards key does not work on gnome-shell 45 about advanced-alttab-window-switcher

[G-dH]

Turned out the issue was that I didn't notice a change in the arguments of the global.display.get_keybinding_action() method in GS 45. Fixed in main, I'll update the e.g.o package soon.

[G-dH]

@lvanderree

Switch windows of an application is logically a part of the app switcher. Therefore, the Tab key switches you to the app mode, allowing you to switch to another app.

In the window switcher mode, the backtick key allows you to switch between applications while staying in the window switcher mode. It groups the listed windows by apps and switches between the first windows of each app. I initially created the switcher for windows only, providing the capability to switch between apps using this approach.

[lvanderree]

@G-dH Thank you for your fast reply and insights in how it was designed.

I've just confirmed that backticking in window-switcher-mode rearranges the windows per app. I did not notice that yet, but nice done!

Then we can keep this issue closed, and I have to be more careful not accidentally pressing TAB when switching windows within an app.

[G-dH]

Seems like I fixed one issue and created another one.. Thanks for reporting this.

[lvanderree]

I've upgraded 21 commits ( 5a5b805..2166b95 ) and now with the Switch windows of an application it now is possible again to press the switch key (in my case ALT + backtick) more than once! I can also go backwards (ALT + SHIFT + backtick) again! Great!

However, when I am in the Switch windows of an application-screen, and I press switch windows (ALT + (SHIFT + ) TAB), I leave the Switch windows of an application-screen , which I would like to have stayed in (just like the other way around, when I am in switch windows-screen via ALT+TAB and press ALT+backtick I stay in switch windows). However I don't get the switch windows-screen either, but I get the switch application-screen, that I don't have setup to show up, and don't want to see either way. Is this some misconfiguration on my side, or intentional, or maybe a (new) bug?