-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Memory meter overflowing/overlaping topbar #127
Comments
Same issue. The "disappear time" is exact the update/refresh time. It only happens when I switch from an full-screen window back to desktop(on my computer).
|
I've been able to reproduce this, I'm gonna fix it soon! Thank you! |
In case it helps identify the cause, I've observed that the amount of overflow is strongly correlated with the amount of time that I spend in fullscreen, eventually reaching the bottom of my display if I spend over an hour in fullscreen. |
I've been looking into this and I think I know how it can be fixed. I think in repaint function the height is huge after going from full screen so it needs to be capped like this: const maxHeight = height > 64 ? 64 : 0; and then use the maxHeight instead of height provided by the system. Maybe I'm wrong, but still worth to try. 64 is arbitrary number I came up with. |
@eboye This bug needs a proper fix. If the user has dash-to-panel with 100px height, capping to 64 will cut the bars. Gnome is very customizable and I cannot set an arbitrary value. I actually debugged and worked on this on july, but couldn't solve it easily, but I'm gonna work on this again now, cuz it's a very bothering bug. |
I know, I just pointed to where the problem might be lying |
I found a temporary solution to this. Gonna come back taking a deeper look at this at a later time, but the resize of the bars are now disabled whenever an app goes fullscreen on the very same monitor. |
Memory meter overlaps the topbar, sometimes even taking the entire height of the screen. Happens when switching workspaces and disappears in ~5secs
The text was updated successfully, but these errors were encountered: