On 30/11/14 09:35, "Olivier Goffart" wrote:
>On Sunday 30 November 2014 06:37:11 Kevin Kofler wrote:
>> Sze Howe Koh wrote:
>> > I'm curious about the rationale behind this API design. I can't think
>> > of any other Qt function that returns an implicitly-shared object by
>> > pointer, so this se
Hi Gunnar,
Note that the results between versions may not be directly comparable.
The benchmark does some very specific things, including destroying the
engine and clearing all type registrations between each run. This is
intended to simulate "application startup performance" conditions, but is
See https://codereview.qt-project.org/#/c/101048/ - huge thanks to Matt
Vogt for his help with debugging and fixing the issues.
Juha, does that resolve the issues for you? Gunnar Roth, does that fix the
issues on Windows? I haven't tested there.
www.qinetic.com.au - Qt And QML User Experience Sp
The loop was due to the QtQuick2 plugin's defineModule() code initializing
the value type providers on load, but not deinitializing them on dtor,
resulting in future loads of that plugin adding the same ptr to the linked
list as the head's next ptr (so, cycle).
The attached diff fixes that issue, b
Null pixmap actually means "no pixmap" (though there is a QPixmap instance,
with null pixmap data). Clearly, the API should be changed to QPixmap
QLabel::pixmap().
Regards,
Konstantin
2014-11-30 22:21 GMT+04:00 Yves Bailly :
> On 30/11/2014 09:35, Olivier Goffart wrote:
> > On Sunday 30 November
On 30/11/2014 09:35, Olivier Goffart wrote:
> On Sunday 30 November 2014 06:37:11 Kevin Kofler wrote:
>> Sze Howe Koh wrote:
>>> I'm curious about the rationale behind this API design. I can't think
>>> of any other Qt function that returns an implicitly-shared object by
>>> pointer, so this seems
Looks like I have to postpone this till tomorrow. IT is doing maintenance work
on the servers, and shut them down.
Note that that as well affects your builds so that they will be interrupted. We
will check the status of the different jobs first thing tomorrow morning and
see if they remained in
Hi
Since the 10.10 mac failures you've been experiencing are caused by Java 8
incompatibility in our current Jenkins
(https://issues.jenkins-ci.org/browse/JENKINS-21341) , I will update our
Jenkins to 1.580.1. This will interrupt the 2 builds that are currently
running, but I'll restage them i
On Sunday 30 November 2014 06:37:11 Kevin Kofler wrote:
> Sze Howe Koh wrote:
> > I'm curious about the rationale behind this API design. I can't think
> > of any other Qt function that returns an implicitly-shared object by
> > pointer, so this seems inconsistent. e.g. QWidget::font() returns a
>
