You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then every container operations (create/move/change layout) would happen in the top-level container (id=20 here). And some fancy tricks can be applied very simply. For example, move all windows in a workspace to another without change the layout:
swaymsg [con_id="20"] move container to workspace number 2
And then with some scripts, a pseudo full screen can be applied, simply by moving all windows to another workspace and moving the previous focused window back. This is also a interesting workaround for issues like fullscreen transparency.
So, is there a more native way to create such a "root" container for workspaces, or any workaround for it? Moreover, this seems to be a non-intrusive feature, perhaps there could be an option for Sway to implement such a feature?
The text was updated successfully, but these errors were encountered:
L-Trump
changed the title
Is it possible to create a "root" container for every workspaces
Is it possible to create "root" container for every workspaces
May 20, 2024
By chance, I found that execute
layout toggle split
twice would create a nested single container like this:Then every container operations (create/move/change layout) would happen in the top-level container (id=20 here). And some fancy tricks can be applied very simply. For example, move all windows in a workspace to another without change the layout:
And then with some scripts, a pseudo full screen can be applied, simply by moving all windows to another workspace and moving the previous focused window back. This is also a interesting workaround for issues like fullscreen transparency.
So, is there a more native way to create such a "root" container for workspaces, or any workaround for it? Moreover, this seems to be a non-intrusive feature, perhaps there could be an option for Sway to implement such a feature?
The text was updated successfully, but these errors were encountered: