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 platf
On 22/02/2019 15.19, Jason H wrote:
> 1.
> '''
> void QLayout::addItem(QLayoutItem *item)
> ...
> void QLayout::addWidget(QWidget *w)
> Adds widget w to this layout in a manner specific to the layout.
> This function uses addItem().
> '''
>
> How can addWidget(QWidget *w) use addItem(QLayoutItem
On Friday February 22 2019 20:31:57 Jason H wrote:
>removeItem: Note: The ownership of widget remains the same as when it was
>added.
This is the part that isn't clear. "Ownership [as] when it was added", I
decided that this had to mean "before it was added" instead of "after it was
added" bec
> Sent: Friday, February 22, 2019 at 4:29 PM
> From: "Giuseppe D'Angelo"
> To: "Jason H"
> Cc: interest@qt-project.org
> Subject: Re: [Interest] Taking back a widget from a QBoxLayout?
>
> Il 22/02/19 20:42, Jason H ha scritto:
> > '''
> > When you use a layout, you do not need to pass a parent
Il 22/02/19 20:42, Jason H ha scritto:
'''
When you use a layout, you do not need to pass a parent when constructing the
child widgets. The layout will automatically reparent the widgets (using
QWidget::setParent()) so that they are children of the widget on which the
layout is installed.
Not
> Sent: Friday, February 22, 2019 at 3:10 PM
> From: "Matthew Woehlke"
> To: "Jason H" , "interest@qt-project.org"
>
> Subject: Re: Taking back a widget from a QBoxLayout?
>
> On 22/02/2019 14.42, Jason H wrote:
> >>> https://doc.qt.io/qt-5/layout.html#tips-for-using-layouts
> > From that:
>
On 22/02/2019 14.31, Jason H wrote:
> addItem: Note: The ownership of item is transferred to the layout,
>
> and it's the layout's responsibility to delete it.
> removeItem: Note: The ownership of widget remains the same as when it
> was added.
>
> So addItem parents it as it's own, then removeIte
On 22/02/2019 14.42, Jason H wrote:
>>> https://doc.qt.io/qt-5/layout.html#tips-for-using-layouts
> From that:
> '''
> When you use a layout, you do not need to pass a parent when
> constructing the child widgets. The layout will automatically
> reparent the widgets (using QWidget::setParent()) so
> Sent: Friday, February 22, 2019 at 2:27 PM
> From: "Giuseppe D'Angelo via Interest"
> To: interest@qt-project.org
> Subject: Re: [Interest] Taking back a widget from a QBoxLayout?
>
> Il 22/02/19 19:04, René J.V. Bertin ha scritto:
> >> I am not 100% sure, it's been a while, but I would assume
> Sent: Friday, February 22, 2019 at 1:04 PM
> From: "René J.V. Bertin"
> To: "Jason H"
> Cc: "interest@qt-project.org Interest"
> Subject: Re: [Interest] Taking back a widget from a QBoxLayout?
>
> On Friday February 22 2019 17:45:05 Jason H wrote:
>
> >I am not 100% sure, it's been a while,
Il 22/02/19 19:04, René J.V. Bertin ha scritto:
I am not 100% sure, it's been a while, but I would assume that the layout is
not the true parent, combined is.
The docs aren't exactly clear on this subject, at least not with the sort of
reading glasses I usually have on when I don't exactly wan
And what is the advantage to declare it into the Resources manually? I add my
qml to my .qrc files and then add the .qrc to my resources, SO I end up with a
single listing of the file into my project tree. I add the qrc:/// to the
import path and everything is fine.
Inside my qt.conf:
Qml2Impor
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 t
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 an
On Friday February 22 2019 17:45:05 Jason H wrote:
>I am not 100% sure, it's been a while, but I would assume that the layout is
>not the true parent, combined is.
The docs aren't exactly clear on this subject, at least not with the sort of
reading glasses I usually have on when I don't exactly
Thanks everyone for time, attention and effort!
Am 18.02.2019 um 09:29 schrieb Christian Kandeler:
> I suggest the opposite: Don't have a qrc file at all, but let qmake
> auto-generate it by adding the qml files directly to RESOURCES.
Wow, that's interesting! I've tried that out for starters.
Th
> Sent: Friday, February 22, 2019 at 11:27 AM
> From: "René J.V. Bertin"
> To: "interest@qt-project.org Interest"
> Subject: [Interest] Taking back a widget from a QBoxLayout?
>
> Hi,
>
> Consider
>
> ```
> SomeWidgetClass *a = maybeReturnSomeWidget();
> SomeOtherQWidgetClass *b = maybeReturn
> 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 Q
Hi,
Consider
```
SomeWidgetClass *a = maybeReturnSomeWidget();
SomeOtherQWidgetClass *b = maybeReturnSomeOtherWidget();
QWidget *combined = new QWidget();
QVBoxLayout *layout = new QVBoxLayout();
layout->addWidget(a);
layout->addWidget(b);
combined->setLayout(layout);
if (doWeLikeItCombined) {
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 QDoubleMatrix
On 22/02/2019 01.30, 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 51d40d7e9bdfc63c5109aef5b732aa2ba10f985a:
> http:
Hello,
Can anybody reproduce that QSkyboxEntity is broken in Qt 5.12.1 with
following debug message?
"QTextureImage only supports local url"
Skybox just black.
I can reproduce it with my own application and with qt3d/tests/manual/skybox
___
Intere
> On 22 Feb 2019, at 13:24, Bernhard B wrote:
>
> Many thanks to Tuukka for the Qt Roadmap 2019 blog post
> (https://blog.qt.io/blog/2019/02/22/qt-roadmap-2019/) - very much
> appreciated!
>
> As the mobile part was not explicitly mentioned, I assume that it won't be a
> focusing area for 2
Many thanks to Tuukka for the Qt Roadmap 2019 blog post (
https://blog.qt.io/blog/2019/02/22/qt-roadmap-2019/) - very much
appreciated!
As the mobile part was not explicitly mentioned, I assume that it won't be
a focusing area for 2019 then? :/
Jean-Michaël Celerier schrieb am Fr., 22.
Feb. 2019
> They even included, scripts to build the app. I'm not sure you have to go
quite that far to be compliant, but awesome nevertheless.
You explicitely have to:
LGPLv3 4. e): Provide Installation Information, but only if you would
otherwise be required to provide such information under section 6 of
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
On Fri, 22 Feb 2019, 13:47 Jean-Michaël Celerier, <
jeanmichael.celer...@gmail.com> wrote:
> Cisco did it with an app that uses gstreamer (which is under LGPL) :
> https://itunes.apple.com/ua/app/cisco-jabber/id467192391?mt=8.
> They send it on request, with the proprietary part in a static lib (s
Cisco did it with an app that uses gstreamer (which is under LGPL) :
https://itunes.apple.com/ua/app/cisco-jabber/id467192391?mt=8.
They send it on request, with the proprietary part in a static lib (see at
the end here :
https://github.com/GStreamer/gst-plugins-good/blob/master/README.static-linki
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 51d40d7e9bdfc63c5109aef5b732aa2ba10f
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.
32 matches
Mail list logo
