-
Notifications
You must be signed in to change notification settings - Fork 14
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
Recognize changes in resolution and adapt accordingly #140
Comments
Ah, you are saying the Menu should catch geometry/resolution changes on the fly. Possibly it doesn't do this yet. Of ourse the menu should always span the whole width of the main screen. What is the main screen? The screen the Menu (and Dock) is displayed on. |
No, I'm not asking for any changes - this was working as I expect in version 0.7.0 - I just copied my autostart script from the 0.7.0 install. Did the startup sequence change? If it was working, then the autostart scripts must’ve been firing before the top bar was started, and now in version 0.8.0 they fire after the top bar is started? Could that be? In any case, I wonder if as a workaround I could kill the top bar and restart it? I could add that to the autoexec script. |
|
Yes! That works. Now my desktop is beautiful again :) |
Well, the point it: It should not be neccessary to do this. We need to make it recognize changes in resolution automatically, and adapt accordingly. |
Need to check |
This appears to be working now in 8.1. Thanks! |
Dell Inspiron 3521 helloSystem 0.8.0 (Build 0H284)
I have a script in autostart that runs xrandr to connect to an external monitor:
The problem is that the top menu bar retains the original width from my laptop 1366 rather than display at the width of 1920. Everything else seems aware of the change. It seems like the menu is not picking up the events from xrandr?
I see issue#36, you state “Actually this is the correct behavior - Menu should be displayed on the main screen”, but I’ve disabled the laptop screen:
The text was updated successfully, but these errors were encountered: