Den mån 25 feb. 2019 kl 19:54 skrev Patrick Stinson :
>
> How can I animate the viewable scene rect of a QGraphicsView using screen
> coordinates? This means animating both center pos and scale. This is similar
> to Google Earth where the map scrolls and zooms smoothly from one point to
> anothe
You can also give CBor implementation a look,maybe it could fit your bill too:
https://doc.qt.io/qt-5/qcbormap.html
From: Sylvain Pointeau
Sent: March 1, 2019 4:46 PM
To: Jérôme Godbout
Cc: Qt Project
Subject: Re: [Interest] using a custom class as parameter of signal/slot, used
in QML
On F
On Fri, Mar 1, 2019 at 10:29 PM Jérôme Godbout wrote:
> Why is the struct deleted one the signal is finished? You create a
> structure only for the signal? it’s not an object or data that will outlive
> that call in the end? If so, you really need to make a copiable
> representation of the struct
Why is the struct deleted one the signal is finished? You create a structure
only for the signal? it’s not an object or data that will outlive that call in
the end? If so, you really need to make a copiable representation of the struct.
What kind of data live into your struct? are they all basic
Hello Jerome,
On Fri, Mar 1, 2019 at 5:25 PM Jérôme Godbout wrote:
> Since signal are not sync all the time but can be async, the argument need
> to be copiable to allow this. So you need to be able to copy the arguments
> on the signals. Therefore the QObject is not copiable, they cannot be
> p
So for Android, if that is modified to:
flags: ["ios", "android"].includes(Qt.platform.os) ? Qt.Window | Qt.MaximizeUsingFullscreenGeometryHint : Qt.Window
And the navigation bar is still there and the app is not behind the bar, that would be a bug? The docs don't mention Navigation bar:
'''
It does indeed work!
Thanks!
Sent: Friday, March 01, 2019 at 12:52 PM
From: "Nuno Santos"
To: ekke
Cc: interest@qt-project.org
Subject: Re: [Interest] iPhone XS App area
It works with Qt 5.12
On 1 Mar 2019, at 17:25, ekke wrote:
Am 01.03.19 um 18:06 schrie
It works with Qt 5.12
> On 1 Mar 2019, at 17:25, ekke wrote:
>
> Am 01.03.19 um 18:06 schrieb Jason H:
>> I have an app and the LaunchScreen on the XS/XS Max shows up
>> full-full-screen but then the Qt app only goes full-screen, with the phone
>> reaining the area for home button and the sta
Am 01.03.19 um 18:06 schrieb Jason H:
> I have an app and the LaunchScreen on the XS/XS Max shows up full-full-screen
> but then the Qt app only goes full-screen, with the phone reaining the area
> for home button and the status bar.
>
> What do I need to do to get Qt to take the full area? My c
I have an app and the LaunchScreen on the XS/XS Max shows up full-full-screen
but then the Qt app only goes full-screen, with the phone reaining the area for
home button and the status bar.
What do I need to do to get Qt to take the full area? My code worked for the
X
_
Since signal are not sync all the time but can be async, the argument need to
be copiable to allow this. So you need to be able to copy the arguments on the
signals. Therefore the QObject is not copiable, they cannot be passed as
arguments directly, you need a pointer. The ownership and lifetime
Hello Jerome,
On Fri, Mar 1, 2019 at 3:34 PM Jérôme Godbout wrote:
> The fact that the QObject is non copiable, is one of the reason it need a
> pointer (which can be copied). As for the ownership, you can check with the
> qqmlengine:
>
> https://doc.qt.io/qt-5/qqmlengine.html#objectOwnership
>
Hi Sylvain,
It is not so complicated, when passing an object instance to QML (it can only
by pointers of QObject based classes), if the instance doesn’t have a parent,
the QML Engine take ownership of the object and delete if when it is no more
needed.
If the instance has a parent, then QML Eng
On Friday, 1 March 2019 01:52:00 PST Alexander Rössler wrote:
> However, for some reason the build fails at:
> qsimd_p.h:196:14: fatal error: 'x86intrin.h' file not found
> #include
> ^
Your compiler is broken. You have Q_PROCESSOR_X86 defined but you don't have
.
--
Hi Jason,
thank you for the link, I did have a look but they are doing the same, with
a comment "// parent-less QObject -> ownership transferred to the JS engine"
but what if there was no connection, or consumed by another object, then I
guess there will be a memory leak?
I don't feel comfortabl
I find it easier the other way ;-)
whereever it is possible, I'm using QObject* for my data
there's a special C++ DataManager class with Q_INVOKABLE methods to
create / delete / and this class always is the parent of my QObject*
it's cool - there's no by-value copying between C++ and QML and
Some of us at the Qt Company are coming together for a workshop about
our documentation, on 11th and 12th March. If you want more information,
I've posted a short blog about it today [0]. Also, feel free to shoot me
an email or ping me on IRC [1] if you have ideas or suggestions.
Paul
--
[0] h
Check out qtmultimedia/examples/multimedia/video/qmlvideofilter_opencl fo the filter result types. I think that's what you want?
I find it easier to code and work with to just rely on QVariant conversion. QVariantList and QVariantMap are transparently converted to JS Objects.
Sent: Friday,
The fact that the QObject is non copiable, is one of the reason it need a
pointer (which can be copied). As for the ownership, you can check with the
qqmlengine:
https://doc.qt.io/qt-5/qqmlengine.html#objectOwnership
You can change the ownership too with setOwnership(). I for one exposed the
me
Can confirm that I could build WASM successfully on linux with yesterday's
5.13 qtbase (and same emscripten version than OP), however I encountered
this while running : https://bugreports.qt.io/browse/QTBUG-74131?filter=-2
Best,
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Fri, Mar
Dear all,
I understood how to use a struct / simple class as a parameter of a signal
/ slot, and it works well by value.
However as soon as we have to declare the type for QML, it is not good
anymore.
It seems that it must be derived from QObject and passed by pointer.
Do I understand well that
Hi,
I experienced the same last week. If you choose a current 5.13 branch of
qtbase, it should work.
Also the latest qt5.git integration contains a build fix for this.
Hence, I’d recommend to switch to 5.13 and use latest emscripten SDK.
Maurice
From: Interest On Behalf Of Alexander Rössler
Hello, Qt devs,
A couple of devs, including me, tried to build and install Qt for WA under
a recent Ubuntu.
See: https://forum.qt.io/topic/100061/ubuntu-compile-qt-failed
We all followed the instructions from the blog post:
https://blog.qt.io/blog/2018/11/19/getting-started-qt-webassembly/
Howe
23 matches
Mail list logo