On Sat, Nov 28, 2015 at 3:07 AM, René JV Bertin wrote:
>
>
> On 28 Nov 2015, at 01:07, Olivier Goffart wrote:
>
>>>
>>> A pure KF5 system will not have ~/.kde*/share/config/kdeglobals, correct?
>>
>> That code was written for integrating into KDE 4.
>> It was not adapted to work with Plasma 5.
>>
On 28 Nov 2015, at 01:07, Olivier Goffart wrote:
>>
>> A pure KF5 system will not have ~/.kde*/share/config/kdeglobals, correct?
>
> That code was written for integrating into KDE 4.
> It was not adapted to work with Plasma 5.
>
> A pure KF5 appliation would anyway use the KDE platform theme
On Saturday November 28 2015 01:07:17 Olivier Goffart wrote:
> > A pure KF5 system will not have ~/.kde*/share/config/kdeglobals, correct?
>
> That code was written for integrating into KDE 4.
That much was clear :)
> A pure KF5 appliation would anyway use the KDE platform theme plugin provided
On Friday 27. November 2015 23:39:07 René J.V. Bertin wrote:
> Digging through Qt's source code to figure out if and how I can get KF5
> applications to honour theming settings on OS X, I observe the following in
> class QKdeThemePrivate in qgenericunixthemes.cpp:
>
> static QString kdeGlobals
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126189/
---
Review request for KDE Frameworks and David Faure.
Bugs: 355508
https
Digging through Qt's source code to figure out if and how I can get KF5
applications to honour theming settings on OS X, I observe the following in
class QKdeThemePrivate in qgenericunixthemes.cpp:
static QString kdeGlobals(const QString &kdeDir)
{
return kdeDir + QStringLiteral(
On Friday November 27 2015 22:31:09 René J.V. Bertin wrote:
Further observation: my font selection is also affected. The only way to get
"my" widget style, fonts and colours by default is by using the Qt's Xcb plugin
(unsupported, but currently it still builds) and setting KDE_FULL_SESSION=true
Hi,
Apologies is this is a bit off-topic:
How does one set/define the default widgetStyle for KF5 applications? I'm now
at the point where have been able to build a style (QtCurve), and can request
it via the --style argument when launching the few example applications I have
(not kdebugdialog5
On Thu, November 26, 2015 13:16:04 Martin Graesslin wrote:
> we are facing a problem during the startup of Plasma on Wayland. If OOM
> protection is enabled for kdeinit and we already have a running X server,
> kdeinit freezes dead.
>
> I'm sorry for having ignored the issue for too long and had j
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126185/#review88898
---
Ship it!
Thanks for moving the template macro to the ECM modu
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126185/
---
(Updated Nov. 27, 2015, 3:55 p.m.)
Review request for KDE Frameworks, Pla
On November 27, 2015 01:02:31 PM Alexander Richardson wrote:
> Has anyone done measurements on a recent system? Does it give any
> noticable benefit?
I have not, nor are my machines good representations. I don't think
considering machines with 2G of memory with older processors to be out of line
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126185/#review88896
---
`end*()` shouldn't have anything in the parenthesis.
https://
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126185/
---
Review request for KDE Frameworks, Plasma and Aleix Pol Gonzalez.
Reposit
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126184/
---
Review request for KDE Frameworks and David Faure.
Bugs: 352882
https
On 26 November 2015 at 18:51, Alex Merry wrote:
> On 2015-11-26 09:27, René J.V. Bertin wrote:
>>
>> There's something I don't really understand though: the exact same
>> question you asked above.
>> What's the difference between starting kwrite directly on the
>> commandline (or through execve())
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125766/
---
(Updated Nov. 27, 2015, 12:07 p.m.)
Status
--
This change has been m
GENERAL INFO
BUILD FAILURE
Build URL:
https://build.kde.org/job/kded%20master%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/27/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Fri, 27 Nov 2015 11:55:07 +
Build duration: 1 min 4 sec
CHANGE SET
Revision 51263f0362884f3d95184b4d1db1966c41ba
GENERAL INFO
BUILD FAILURE
Build URL:
https://build.kde.org/job/kded%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/29/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Fri, 27 Nov 2015 11:55:07 +
Build duration: 1 min 12 sec
CHANGE SET
Revision 51263f0362884f3d95184b4d1db1966c41bace96 b
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125766/
---
(Updated Nov. 27, 2015, 11:52 a.m.)
Review request for KDE Frameworks.
2015-11-25 18:53 GMT-03:00 David Faure :
> On Saturday 21 November 2015 15:50:31 Luiz Romário Santana Rios wrote:
>> , or make the waitFor* calls and warn the user
>> that passing a QIODevice which is not yet fully ready to
>> KCompressionDevice might make KTar::open() block.
>
> That would work I
21 matches
Mail list logo