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

Multi-monitor support: only use active monitor with maximize and full-screen commands #11

Open
rprichard opened this issue Apr 6, 2017 · 4 comments
Labels
enhancement The report requests an enhancement beyond the intended behaviour.

Comments

@rprichard
Copy link

I have two monitors. When I maximize a window or make it full-screen, it occupies both monitors (i.e. the entire virtual desktop/screen). This is way too big, so I'd prefer that the window only occupy one monitor. Other window managers get this right already, so I'm guessing there's some protocol/extension that isn't implemented in blackbox.

Perhaps this issue is a feature request.

I'm currenty using blackbox version 0.72, commit 8c9e2af.

@bbidulock
Copy link
Owner

_NET_WM_FULLSCREEN_MONITORS is not currently supported by BB. Most of the other window managers that I have repos for do support it. BB doesn't really have an idea of monitors: it treats multi-head setups like one big screen. So, yes, I suppose it is a feature request.

@bbidulock bbidulock added the enhancement The report requests an enhancement beyond the intended behaviour. label May 28, 2018
@lucamarogna
Copy link

Wait! This is the main reason I chose blackbox as my WM!

@aniou
Copy link

aniou commented Feb 4, 2020

But it is always possible to compile without XINERAMA extension or even disable it in config (as in following patch). From my point of view using blackbox on two monitors with different resolutions is somewhat inconvenient.

Speaking of patch - it is not mine and I don't even tried it, but maybe it may be a starting point?

@stainless81
Copy link

Speaking of patch - it is not mine and I don't even tried it, but maybe it may be a starting point?

I used that patch a long long time ago and had moderate success with it. An earlier patch against 0.65 seemed to work better on my hardware at the time.

This is a feature I too would like to see added to Blackbox, even if a runtime or compile time switch were needed to enable it. There is at least one machine where I've switched to Fluxbox because of this feature. I still much prefer using Blackbox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The report requests an enhancement beyond the intended behaviour.
Projects
None yet
Development

No branches or pull requests

5 participants