[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 299001] White text in gtk3 apps while in Unity
From:       Hugo Pereira Da Costa <hugo.pereira () free ! fr>
Date:       2012-04-30 17:45:14
Message-ID: bug-299001-17878-YQHwvlSqKD () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=299001

--- Comment #27 from Hugo Pereira Da Costa <hugo.pereira@free.fr> ---
@Russlan, if gtk_settings_get_default fails yes, all loading of the settings
from OxygenQtSettings will fail
(cause we write directly to this guy and not to a css file)
Notably all the color settings that are read from kdeglobals.

http://developer.gnome.org/gtk3/stable/GtkSettings.html#gtk-settings-get-default

Is the documentation.
It returns NULL if no screen is defined.
Might be a unity hack.
Maybe the theme gets loaded/initialized too early.

The "return 0" from QtSettings usually happens when settings have already been
initialized and is called a second time.
What we (you :)) could try:
at the top of QtSettings::initialize, and before setting initialized to true,
check the validity of gtk_settings_get_default() and gdk_screen_get_default(),
and return false if they are invalid.
If the method is called again, later, at least it would try again to redo the
full thing. Makes sense ? Maybe this time the screen will be valid.
and if not, it would be up to us to make sure that the method is called again
and again until the screen is valid 
(this should happen, at some point ;))

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]