On Mon, Dec 9, 2019 at 1:06 PM Lukast dev wrote:
> But stack sampling sometimes sucks because you don't see if the function
> was called million times and thus it shows up in the profile
> or it is called once and is expensive and thus it shows up as hot spot.
> That's the benefit of tracing wher
Hi Simon,
After qtbase and before others. I do not foresee examples in qtbase relying on
it in the near future, simply because that would mean examples using QRhi, and
that’s all private API so such examples are unlikely to appear. Internally,
there are QRhi-related manual/auto tests in qtbase,
Hi,
Great :)
In the chain of dependencies, do you see this right after qtbase and before for
example qtdeclarative?
Or do you foresee any use of the shader compiler in qtbase itself? I suppose at
least for some examples it would make sense, which makes me wonder if those
examples should move
Hi all,
I would like to suggest promoting Qt Shader Tools (currently
qt-labs/qtshadertools [1]) into a proper Qt module for Qt 6.0.
Qt 5.x is not in scope, meaning the new qt/qtshadertools repo would start with
a dev branch only, and is to be ignored for Qt 5.x builds and releases.
As describe
Am 13.06.19 um 09:42 schrieb Lars Knoll:
> Hi all,
>
> After all the discussion, lets go back to the original proposal. We can see
> from the discussions that there is still work to be done, but I can’t find
> anything that sounds like a real showstopper.
>
> The two missing features that were v
Hi!
We have updated Qt 5.14.0 RC2 in the production today. Delta to RC1 as an
attachment
br,
Jani Heikkinen
Release Manager
From: Releasing on behalf of Jani Heikkinen
Sent: Wednesday, December 4, 2019 3:02 PM
To: development@qt-project.org; releas...
