On Tue, 26 Feb 2019 at 05:37, Jason H wrote:
>
> > Sent: Friday, February 22, 2019 at 4:27 AM
> > From: "Christian Gagneraud"
> > Would you consider making arm v8 the minimum requirement for Qt6?
>
> You might anger the raspberry pi people who still use ARM11 in the Pi Zero,
> and other
> Sent: Friday, February 22, 2019 at 4:27 AM
> From: "Christian Gagneraud"
> Would you consider making arm v8 the minimum requirement for Qt6?
You might anger the raspberry pi people who still use ARM11 in the Pi Zero, and
other embedded users. I don't see 32bit arm cores going away any time
On Friday, 22 February 2019 01:27:49 PST Christian Gagneraud wrote:
> > One of the two reasons the commit message says was to avoid the surprise
> > in
> > that it used float in embedded platforms (read: ARM). That rationale is no
> > longer applicable, as we changed qreal to be double in all
Il 22/02/19 12:01, Uwe Rathmann ha scritto:
Actually there are several versions of Qt5 that do not even compile when
setting qreal=float. After reporting such a bug the fix did not even go
into the relevant LTS version ( Qt 5.9 at that time ).
Obviously building with qreal=float seems not to be
Il 22/02/19 19:27, Matthew Woehlke ha scritto:
We*almost* had that with QVectorNd and QMatrixNxN... until Qt5 went and
made them float. Sigh.
*Deliberately*, to target GPU programming, where the only things that
matter (de facto) are floats.
What I would*really* love is to see Eigen or
On 22/02/2019 11.39, Jason H wrote:
> Well I think if you want such things eigen
> (http://eigen.tuxfamily.org/index.php?title=Main_Page) is what you
> need. However, I would love to see Qt incorporate some basic
> operations.
We *almost* had that with QVectorNd and QMatrixNxN... until Qt5 went
> On 22/02/2019 04.08, Paolo Angelelli wrote:
> > You aren't telling us much, except that you need to invert it and multiply
> > points with it.
> > If QtPositioning-private is an acceptable dependency instead of pulling in
> > eigen (or others),
> > you could probably get away with the private
On 22/02/2019 04.08, Paolo Angelelli wrote:
> You aren't telling us much, except that you need to invert it and multiply
> points with it.
> If QtPositioning-private is an acceptable dependency instead of pulling in
> eigen (or others),
> you could probably get away with the private
On Fri, 22 Feb 2019 22:27:49 +1300, Christian Gagneraud wrote:
> If you do not want to support qreal=float anymore, please do not allow
> ./configure to make that choice and maybe get rid of qreal typedef,
> and delete qreal from Qt6 API while you're at it.
Actually there are several versions of
Il 21/02/19 22:47, Matthew Woehlke ha scritto:
So... after a full day of debugging, trying to port my Qt4 app to Qt5
and chase down a nasty case of stack clobbering, I discovered that the
problem is that QMatrix4x4 changed from qreal to float.
(Uh...why? I am not particularly amused by the loss
On Fri, 22 Feb 2019 at 19:34, Thiago Macieira wrote:
>
> On Thursday, 21 February 2019 13:47:05 PST Matthew Woehlke wrote:
> > (Uh...why? I am not particularly amused by the loss of precision, nor
> > the extremely subtle incompatibility.)
>
> Changed in commit
You aren't telling us much, except that you need to invert it and multiply
points with it.
If QtPositioning-private is an acceptable dependency instead of pulling in
eigen (or others),
you could probably get away with the private QDoubleMatrix4x4 that is in there,
basically
a double QMatrix4x4.
On Thursday, 21 February 2019 13:47:05 PST Matthew Woehlke wrote:
> (Uh...why? I am not particularly amused by the loss of precision, nor
> the extremely subtle incompatibility.)
Changed in commit 51d40d7e9bdfc63c5109aef5b732aa2ba10f985a:
http://code.qt.io/cgit/qt/qtbase.git/commit/?
So... after a full day of debugging, trying to port my Qt4 app to Qt5
and chase down a nasty case of stack clobbering, I discovered that the
problem is that QMatrix4x4 changed from qreal to float.
(Uh...why? I am not particularly amused by the loss of precision, nor
the extremely subtle
14 matches
Mail list logo
