On Saturday 04 January 2014 20:52:43 David Faure wrote:
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote:
The first problem is that with kf5, the style configuration kcm expects
a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it
was
On 01/05/2014 09:42 AM, Martin Graesslin wrote:
On Saturday 04 January 2014 20:52:43 David Faure wrote:
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote:
The first problem is that with kf5, the style configuration kcm expects
a libkstyle_oxygen_config.so *plugin* for this
On 01/04/2014 11:21 PM, Dominik Haumann wrote:
On Saturday 04 January 2014 23:11:14 David Faure wrote:
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote:
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote:
ok. So this should go to kstyle (nothing oxygen explicit in
On 01/05/2014 09:57 AM, Hugo Pereira Da Costa wrote:
On 01/05/2014 09:42 AM, Martin Graesslin wrote:
On Saturday 04 January 2014 20:52:43 David Faure wrote:
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote:
The first problem is that with kf5, the style configuration kcm
On Sunday 05 January 2014 10:10:48 you wrote:
On 01/05/2014 09:57 AM, Hugo Pereira Da Costa wrote:
On 01/05/2014 09:42 AM, Martin Graesslin wrote:
On Saturday 04 January 2014 20:52:43 David Faure wrote:
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote:
The first problem is
On Sunday 05 January 2014 10:04:00 Hugo Pereira Da Costa wrote:
On 01/04/2014 11:21 PM, Dominik Haumann wrote:
On Saturday 04 January 2014 23:11:14 David Faure wrote:
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote:
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa
On Saturday 04 January 2014 23:04:50 Nicolás Alvarez wrote:
2014/1/4 David Faure fa...@kde.org:
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote:
What I personally would like more is to always be able to read this.
I of course can use a KSharedConfig::openConfig() and then read
Hi Dominik,
there are two issues in what you describe
1. There was an error loading the configuration dialog for this style:
Unknown error.
2. QStyle::SH_Widget_Animate
The first problem is that with kf5, the style configuration kcm expects
a libkstyle_oxygen_config.so *plugin* for this
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote:
The first problem is that with kf5, the style configuration kcm expects
a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it
was kstyle_oxygen_config.so in kde4 times.
now, as the error message indicates:
On 01/04/2014 08:52 PM, David Faure wrote:
On Saturday 04 January 2014 20:19:43 Hugo Pereira Da Costa wrote:
The first problem is that with kf5, the style configuration kcm expects
a libkstyle_oxygen_config.so *plugin* for this configuration, whereas it
was kstyle_oxygen_config.so in kde4
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote:
KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings);
return g.readEntry(GraphicEffectsLevel, 0);
The default value is wrong.
In KDE4 it was enabled by default.
(see
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote:
ok. So this should go to kstyle (nothing oxygen explicit in there).
In fact, kstyle returns:
KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI Settings);
return g.readEntry(GraphicEffectsLevel, 0);
mmm. No clue
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote:
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote:
ok. So this should go to kstyle (nothing oxygen explicit in there).
In fact, kstyle returns:
KConfigGroup g(KSharedConfig::openConfig(), KDE-Global GUI
On Saturday 04 January 2014 23:11:14 David Faure wrote:
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote:
On Saturday 04 January 2014 20:56:30 Hugo Pereira Da Costa wrote:
ok. So this should go to kstyle (nothing oxygen explicit in there).
In fact, kstyle returns:
2014/1/4 David Faure fa...@kde.org:
On Saturday 04 January 2014 23:02:35 Dominik Haumann wrote:
What I personally would like more is to always be able to read this.
I of course can use a KSharedConfig::openConfig() and then read the config
value myself. However, would it be of interest to
15 matches
Mail list logo
