-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
unite-shell overrides panel theme #134
Comments
investigated a bit further and the "Main.panel.set_style" lines (2x) in themeMods seems to be the cause. I have commented both and things appear rather normal now. |
Without the two Main.panel.set_style lines there everything seems to be in working order if not for some weird spacing issue on mouse-over. That one is reported already in dash-to-panel: |
Hi @freddyw, thanks for the report. I have added a solution to the issue. Can you try it? Thanks |
I cloned the master branch and tested on 3.32 (fedora 30) and 3.34 (fedora 31). Seems to work pretty reliable now (apart from 1 missing panel icon for autokey in 3.34, dunno what causes that). A big thanks for the quick fix. |
@jonian 1- [git pull to update my local repo..and]...I can confirmed this solution sorted my issues with weird fonts sizing + background panel (I used dynamic-panel-transparency ext fwiw). Thank you for the solutions...really appreciated! |
Not sure how to best describe the issue but here it goes. I am using unite-shell and dash-to-panel. I have a custom panel theme background color set in dash-to-panel. Since unite-shell v32 the panel background is set to black after a fresh reboot. Restarting gnome-shell (with ALT-F2 r) restores the custom background as set in dash-to-panel. I have been trying to pinpoint where things go wrong and it looks like line 21 in modules/themeMods.js is the culprit:
this._signals.connect(this.gtkSettings, 'notify::gtk-font-name', 'setPanelStyle')
as soon as I comment that line the panel (and background) looks fine (except the fonts offcourse). I have tried experimenting with disabling/enabling the "Apply system fonts to shell theme" but that does not seem to have any effect. Any idea what might be causing this rather odd incompatibility?
The text was updated successfully, but these errors were encountered: