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
We could consider adding a switch to enable / disable dynamic workspaces here.
It seems like there are people who like to set up their workspaces at the beginning and never rearrange them again and people who actually want a "dynamic" behaviour.
This could change e.g the current way of cycling through dynamic workspaces. Currently, cycling with Super+Tab doesn't cycle through the empty workspace even when dynamic workspaces are enabled. Adding an option would split this behaviour and make cycling the empty workspace based on the type of workspace behaviour used.
The text was updated successfully, but these errors were encountered:
I think there's a lot of other implications to consider here. If we start supporting static workspaces then people will want to set different wallpapers per workspace, they'll want to launch apps to a certain workspace number, grid view starts to make sense again, etc etc etc. A static workspace setup is a pretty different workflow and I think it implies a huge scope of work.
If the concern is being able to quickly get to a new workspace with a one-handed shortcut I think that would be much easier solved by adding a new shortcut. It looks like maybe Super D is unused
We could consider adding a switch to enable / disable dynamic workspaces here.
It seems like there are people who like to set up their workspaces at the beginning and never rearrange them again and people who actually want a "dynamic" behaviour.
This could change e.g the current way of cycling through dynamic workspaces. Currently, cycling with Super+Tab doesn't cycle through the empty workspace even when dynamic workspaces are enabled. Adding an option would split this behaviour and make cycling the empty workspace based on the type of workspace behaviour used.
The text was updated successfully, but these errors were encountered: