Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retain Workspaces on Primary Display Only as an Option #932

Open
starr-dusT opened this issue Aug 23, 2024 · 7 comments
Open

Retain Workspaces on Primary Display Only as an Option #932

starr-dusT opened this issue Aug 23, 2024 · 7 comments
Labels
enhancement Adds a new feature or extends scope

Comments

@starr-dusT
Copy link

I really like the idea of the extensions, but have issues with multi-monitors. I assume it is part of the fighting default behavior of Gnome, but windows flash/appear/disappear on the other monitor when workspaces are changed. I find this distracting and would like to restrict workspaces to a single screen (as-is one of the default multi-monitor modes in Gnome). I'd be willing to look into trying to implement this, but would like a first pass opinion if it would be an untenable add for one reason or another or perhaps I'm missing a way this can be done already. Thanks!

@starr-dusT starr-dusT added the enhancement Adds a new feature or extends scope label Aug 23, 2024
@jtaala
Copy link
Collaborator

jtaala commented Aug 24, 2024

I assume it is part of the fighting default behavior of Gnome, but windows flash/appear/disappear on the other monitor when workspaces are changed

Very much. I'm assuming you are referring to coming our of Gnome overview? (the window flashing). We've toyed with creating our own "overview".

Supporting workspaces on primary display only is a good request. We've had basic support previously but some issues weren't resolved, so PaperWM disables that option when starting up.

Not really untenable, and could alleviate the issue you mentioned above (and would be easier than implementing our own overview).

@rawkode
Copy link

rawkode commented Aug 26, 2024

Potential duplicate of #216

@starr-dusT
Copy link
Author

starr-dusT commented Aug 29, 2024

Thanks @rawkode. I don't think this is exactly the issue they were having there. Maybe I'm being precious, but I've attached a video of what I'm seeing. This is a capture of my second monitor on workspace 2 while I cycle between workspace 1 and 3 on the primary monitor. You can see the chrome window pop in and out. I think this is expected behavior, but I haven't seen anyone explicitly mention it and that surprises me because I find it distracting. Is this the expected behavior @jtaala or @rawkode? Thanks for taking the time I really appreciate the work you all are doing.

Screencast.from.2024-08-28.19-54-08.webm

@jtaala
Copy link
Collaborator

jtaala commented Aug 29, 2024

Is this the expected behavior @jtaala or @rawkode?

No. Then again, you're not actually using PaperWM's workspace switching model (how are you workspace switching? e.g. what keybinds are you using?).

PaperWM has it's own workspaces switching paradigm, where workspaces are vertically stacked on each monitor - e.g. this is what it looks like:

Screencast.from.2024-08-29.22-24-46.mp4

The default keybinds for switching to above/below workspaces are super+page_up, super+page_down. You can change those to any preferred keybinds:

image

Note, you can choose different switching behaviours (e.g. switch between workspace assigned to all monitors, or just the current monitor etc.

@starr-dusT
Copy link
Author

starr-dusT commented Sep 2, 2024

Ahh... that makes sense. I'm switching work spaces with custom key binds on Super + 1,2,3... like this:

image

Using the PaperWM key-binds work as expected. I might have missed documentation on that, my bad. If the built-in key-binds aren't intended to be supported this can be closed. Thanks for the help and great project!

@jtaala
Copy link
Collaborator

jtaala commented Sep 3, 2024

Yes, it is intended that with PaperWM, the paperwm keybinds for switching windows is used. Although, I'm just trying to remember why we don't have keybinds to switch to workspaces directly (e.g. switch to workspace 1 etc.).

@Thesola10
Copy link
Collaborator

Could be made into a toggle for #753

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adds a new feature or extends scope
Projects
None yet
Development

No branches or pull requests

4 participants