onsah / fullscreen-to-new-workspace

New and maximized windows will be moved to empty workspaces. Supports multiple monitors.
GNU General Public License v3.0
20 stars 10 forks source link

Whitelist/blacklist #8

Open gaussandhisgun opened 1 year ago

gaussandhisgun commented 1 year ago

It would be neat to have some sort of way to define specific windows or applications that should not be affected by the extension, like was described with Waydroid in https://github.com/kaiseracm/gnome-shell-extension-maximize-to-empty-workspace/issues/10 in the "parent" repo. Its especially annoying with Waydroid (in multi window mode) because on screen keyboard is its own (fullscreen!) window that, in conjunction with this extension, gets separated from exactly the thing i should see when typing. To note: this issue also happens on Phosh due to the way their compositor works, so it probably should be fixed on Waydroid's end, but it will take them ages to implement anything remotely similar to WSL's every-app-is-its-own-virtual-monitor approach, so... i'm sure there are a few non-Waydroid cases for this.

Oh, right, i remembered a few more: Cheese's fullscreen flash when doing selfies is one of them. And flameshot (when it works). And a few other things that are drawn as a fullscreen overlay.

queenbiscuit311 commented 1 year ago

Coincidentally, just came here to request this, but for a different reason. Desktop Icons NG's icon panes (both the GTK3 version and the GTK4 fork) are technically full screen background windows, so one of two things happen. If you turn on DING after this extension is already started, it moves the desktop icons to the top and decouples them from the desktop background, causing GNOME to freak out and keep switching your workspaces. It also basically makes the desktop icons be stuck as the foreground window. If both are already on simultaneously or you start this extension after the desktop icons extension, it just breaks the extension entirely.

On GTK3 DING you can fullscreen to an empty workspace, but when you un fullscreen/maximize it doesn't automatically move the window back to the previous workspace. On GTK4 DING the extension just completely ceases to work, acting as if it weren't even enabled. A blacklist/whitelist function would be quite helpful.

queenbiscuit311 commented 3 months ago

Coincidentally, just came here to request this, but for a different reason. Desktop Icons NG's icon panes (both the GTK3 version and the GTK4 fork) are technically full screen background windows, so one of two things happen. If you turn on DING after this extension is already started, it moves the desktop icons to the top and decouples them from the desktop background, causing GNOME to freak out and keep switching your workspaces. It also basically makes the desktop icons be stuck as the foreground window. If both are already on simultaneously or you start this extension after the desktop icons extension, it just breaks the extension entirely.

On GTK3 DING you can fullscreen to an empty workspace, but when you un fullscreen/maximize it doesn't automatically move the window back to the previous workspace. On GTK4 DING the extension just completely ceases to work, acting as if it weren't even enabled. A blacklist/whitelist function would be quite helpful.

This no longer appears to be an issue, at least on GTK4 Desktop Icons NG. everything is working as expected with the extension enabled