feat: option to remove tabbed layout dragdrop

[moritztim]

(1) Issue/Bug Description/Video Capture/Screenshots:
When I make a tabbed window out of 2 windows, then drag one out, the other window remains tabbed.
(2) Steps to reproduce (if you know):

1. move 1 window ontop of the other until the blue preview shows up
2. let go
3. remove the window again
   (3) Distribution and Linux version:

n/a
(4) Journal Logs from the last hour:

n/a
(5) Gnome Shell version:

45
(6) Forge version and where was Forge installed from:

extensions.gnome.org
(8) Monitor Setup (2 x 1080p, 4K, Primary(Horizontal), Secondary(Vertical), etc):

n/a
(9) Other Installed/Enabled Extensions:

n/a
(10) Other Notes:

n/a

[jmmaranan]

Hi @moritz-t-w, this is expected behavior. It does not automatically remove the tab. You have to press the keybindings to remove. Or move the window into the next container

[moritztim]

What's the use case? Why would I want a tab bar at the top of my single window? It doesn't add information since the name is already in the titlebar and it doesn't change the behaviour, because you can still create tabbed windows the same way regardless of whether it's already tabbed or not

[jmmaranan]

No use case. The tabbed layout is originally triggered and removed by keybindings. Intents are always explicit. It is not difficult to add a setting to make automatic if someone wants it.

[moritztim]

The tabbed layout is originally triggered and removed by keybindings. Intents are always explicit.

The default Drag-and-Drop Center Layout is Tabbed. That's how I've been doing it. So it would be more consistent too if moving it back out undid the tabbed layout

[moritztim]

Intents are always explicit.

Sure. But does it make sense to create a scenario that has no use case, just to enforce this? The user will always either disable it or not care for it, so there’s no reason not to do that for the user

[jmmaranan]

I have the changes locally to untab the layout via dnd. There are other considerations like keyboard users, and stacked layout. I will add them as well as part of the changes.

[jmmaranan]

Intents are always explicit.

Sure. But does it make sense to create a scenario that has no use case, just to enforce this? The user will always either disable it or not care for it, so there’s no reason not to do that for the user

What's also missing is the ability to untab everything via mouse and not just moving the last window out via dnd.

Forge borrowed a lot from i3 but mostly concentrating on keyboard movements. Since dnd was added later, it is unfortunately incomplete, for sure the ability to untab via dnd. It also depends on my use case, some of the requests I do not use daily. So untabbing via dnd is not there. But here we are. Let me test it a bit