When i click on the space bar, the extension plot white boxes and i can't see the letter written inside them.

This is because the font color and the background color are both white by default. It can be easily fixed by update those default color.

I'm using fedora 31 with gnome 3.34.3

When the option Show Window Selector when show Overview option is enabled, and when Overview animations are on, the letter indicators seem to appear a little too soon and disappear a little too late. That is, when entering Overview, the indicators appear before the animation is even finished, and when exiting Overview, they don't disappear until the animation is over. Not as noticeable if animations are sped up (e.g. with Impatience), but just a minor observation.

Hello,
Great work, I love it.
I would love to have the ability to close a window in the overview in a similar way.

I am not familiar with the gnome API, but I am JS developper myself. I may give it a try if it is not too time consuming.

Hi, this extension doesn't work in gnome shell 40 (currently testing this on Fedora 34 beta).

Thanks for this helpful extension. It works well if there's only one display active, but if I'm using both an external display and my laptop display, it no longer works. Hitting space to show/hide the letters works, but typing a letter doesn't do anything, and hitting shift (to close) doesn't do anything. Just wanted to report the bug, in case you weren't aware of it.

I upgraded to gnome 3.38 on Debian Testing and the extension stopped working, appears active but nothing appears when space key is hit

Hi,

thanks for this Extension. I use it daily. However, each time I activate the overview I get these log entries:

Nov 27 15:18:20 hostname gnome-shell[2202]: INFO - [Overview Navigation - CustomWorkspaceView] Animate to overview ...
Nov 27 15:18:20 hostname gnome-shell[2202]: INFO - [Overview Navigation - Search] Enabling search ...
Nov 27 15:18:21 hostname gnome-shell[2202]: INFO - [Overview Navigation - CustomWorkspaceView] On Destroy ...
Nov 27 15:18:21 hostname gnome-shell[2202]: INFO - [Overview Navigation - Search] Enabling search ...
Nov 27 15:18:21 hostname gnome-shell[2202]: INFO - [Overview Navigation - CustomWindowOverlay] Destroying ...

Maybe they can be suppressed?

Is there a way to automatically active this extension every time without having to trigger it with the space bar?

it looks like the generated labels are only chosen from (around) the left part of the home row (a, s, d, f). it would be nice if the labels could be picked from the right part as well (to have an even balance).

It would be nice if the label style would be adjustable.
Maybe by css or just the colors for:

• Font
• Background
• Border

After installing Fedora 30, this extension initially worked just fine but now has stopped working. It still shows the overlay but on pressing the particular key sequence, seemingly nothing happens.

How can I begin to troubleshoot this?

Although the letters on the focusing hint have really good contrast, I find the ones on the closing hint a bit harder to see. Perhaps a brigher red, like the one used by the in the Adwaita-Dark stylesheet (#ff7b63), could improve the visibility a bit. I tested it on a contrast checker and it looks better to me:

Current	Changed

If you like this idea, I already have this branch on my fork ready to PR 😉

I'd love to be able to increase the size of the hints to ridiculous levels so I can more easily notice the keys. =)
I have 2 big screens and it takes time to scan with my eyes across them, I'd like to be able to read the letters with my peripheral vision.

It looks like a s d f are the first letters assigned. This is good for qwerty style keyboards.
I'm using dvorak.
Please add on option to switch to a o e u ...

Hi,

I made a little patch using a lookup table to change the ordering of the labels of the windows. This way the keys are a bit quicker to find IMHO, and similar to how e.g. https://github.com/abo-abo/avy jumps around, perhaps something to consider for future releases.

In windowSelector.js:

this.maptbl = {
	"0": 0, "1": 18, "2": 3, "3": 5, "4": 6, "5": 16,
	"6": 22, "7": 4, "8": 17, "9": 19, "10": 25, "11": 23,
	"12": 2, "13": 21, "14": 1, "15": 24,
	"16": 7, "17": 13,  "18": 20, "19": 9,
	"20": 12, "21": 8, "22": 10, "23": 11,
	"24": 14, "25": 15
};

[snip]

const mod1 = index % this.numberOfDifferentKeys
var mod = parseInt(this.maptbl[mod1])

Hi,

I am usually activating "Shift cancels Caps Lock" keyboard option and when I am in overview, pressing Shift key activates window closing mode. I can only deactivate it when I press both Shift keys together. Is there something you can do about it?

Hey, amazing extension!

Two things that will improve the quality of life even further:

• be able to add a timer for the letters to show up (some 1-2 seconds delay)
• assign an additional button for the app selection (alt/ctrl etc.), so to launch an app it would be ALT + a. This will be good, now it just stops the direct type to search in the overview.

After upgrading to GNOME 3.36, the extension doesn't work anymore. It doesn't error but when pressing Space in the overview, the indicators aren't shown anymore.

I've now enabled logging in the settings but where does the logging output go?

in the simplest case one could let the user choose from a number of predefined positions:

I personally would like to place them right above the application icon.

maybe it's just me, but I only ever want to use this sort of navigation in the regular overview (and not in the application overview).

This might be out of scope of this project and if so, I respect that.

However, personally I'd really like to have the option of numeric selectors for workspaces.

And while at it, if we decide to add this feature, I'd also change how selectors currently work: Let's say I have three windows, A B on workspace 1 and C on workspace 2.

If I'm on workspace 1, I can select C and switch to that window on workspace 2. In practice, I'm not convinced that this is all that useful because the assigned selectors change all the time (because of new and closed windows), so that the user almost has to see the overlayed selector before making their choice. Since they don't see selectors overlayed for windows outside of their current workspace, we might not want to assign any selectors to them.