-
Notifications
You must be signed in to change notification settings - Fork 221
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
[Request] Display Fusion virtual monitor intégration #269
Comments
How does GlazeWM currently behave with DisplayFusion screen splits? Is there 1 bar window or multiple? This sounds very tricky and I'd be hesitant to create a solution specifically tailored for DisplayFusion |
Thanks for your help. Edit : After doing a lot of testing I think it's best not to run both at the same time because on top of that I'm using rulers for each window which makes them float in GlazeWM. |
I think I understand your use case. As of right now, this is not possible. A possible implementation to support this could look like something like a max window width rule. Prevent any managed window from being larger than 1920px for example. So if you have a single horizontal workspace that is 3440px and open up a window, the window would be 1920px wide and centered. Empty space would fill the rest of the screen. This would be a welcome improvement for ultrawide users. |
For now my resolution is 5120 x 1440. I must have empty space on the left and right of the monitor because i work on the middle on the screen and spotify and other thing are on the left and right. |
Hello and thank you for the fabulous work you have done with this software.
Currently I'm using display fusion to split my screen into several parts ( 3 to be exact ).
I would like to know if it is possible that GlazeWM works on the main zone that I have in display fusion and that the two other parts on the left and on the right are interpreted as secondary screens in GlazeWM and that it is possible to send windows to these parts as if simply changing screens.
Thank you so much
The text was updated successfully, but these errors were encountered: