Hi,
I am getting following error, when running Qt 3d app.
05-19 19:26:06.857 17339 17339 W libClimateHMI.so: (null):0 ((null)): Can't
find surface 2
05-19 19:26:06.869 221 628 D AudioFlinger: mixer(0xab962fb0) throttle
end: throttle time(3)
05-19 19:26:06.877 17339 17339 W libClimateHMI.so:
See https://bugreports.qt.io/browse/QTBUG-53649
Em sexta-feira, 13 de maio de 2016, às 09:11:35 PDT, Andy Shaw escreveu:
> Since there does not seem to be any general objections, I have submitted a
> patch for this - https://codereview.qt-project.org/159120 - this is for
> 5.8. If anyone does see
Hi Marc,
On Thursday 26 May 2016 08:32:21 Marc Mutz wrote:
> Hi,
>
> In QAtomic, we use compare_exchange_strong with a single memory_order
> argument. The failure mode is therefore calculated by libctdc++, the
> relevant code in atomic_base.h has not changed from 4.8.0 to 6.1.0, and
> appears to
Hi Tomek,
You're not really missing anything :)
In the case of an asynchronous swapBuffers, there is a slight chance the
wl_buffer release on the next draw pass will be premature, because there is
nothing the qtwayland module that catches when the GPU is done with a frame.
In stack that I'm
I have created a BUG: https://bugreports.qt.io/browse/QTBUG-53646
2016-05-26 12:01 GMT+03:00 Denis Shienkov :
> UPD: Seems the problem is ***NOT IN QtMM***..
>
> For example, when I have compiled an usual cpp-based QMediaPlayer example,
> and to set there:
>
> {quote}
>
On Wed, May 25, 2016 at 04:11:00PM +0200, raven-worx Software wrote:
> i am trying to create a vcxproj-Project of the QtWebKit module.
>
there is no hope whatsoever to get that working.
note that vcxproj support for the build of qt as a whole has been
dropped a while ago, which is reflected by
Hi all,
Is there any mechanism that that synchronises wl_buffer release by the
compositor to the GL driver's pipeline?
I can't figure out how this synchronisation is supposed to work. My initial
thought was that the sequence of actions will be something like this.
The client
sends a new frame to
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Thiago
> Macieira
> Sent: tiistaina 24. toukokuuta 2016 21.22
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.7.0 change files
>
> Em terça-feira,
On Tue, May 24, 2016 at 11:21:58AM -0700, Thiago Macieira wrote:
> Em terça-feira, 24 de maio de 2016, às 10:50:13 PDT, Jani Heikkinen escreveu:
> > I and Antti have now done initial change files for every qt submodule (if
> > not already available). Maintaitainers: Please take those over & modify
Sounds good to me in principle, especially since we very likely have again next
generation of both iOS and OS X to support in Qt 5.8.
Especially in iOS users tend to upgrade to new versions quite quickly (and then
see if their devices still can run that or not).
Yours,
Tuukka
From:
UPD: Seems the problem is ***NOT IN QtMM***..
For example, when I have compiled an usual cpp-based QMediaPlayer example,
and to set there:
{quote}
root@apalis-t30:~/Downloads# export
QT_GSTREAMER_WIDGET_VIDEOSINK=nv_omx_hdmi_videosink
root@apalis-t30:~/Downloads# export
Hi,
In QAtomic, we use compare_exchange_strong with a single memory_order
argument. The failure mode is therefore calculated by libctdc++, the relevant
code in atomic_base.h has not changed from 4.8.0 to 6.1.0, and appears to do
the correct thing. It does use signed bitmasking operations with
12 matches
Mail list logo