The same behavior is when tmp1 is initialized with C++ function.
Function is called twice too.
2018-03-08 8:15 GMT+01:00 Tomasz Olszak :
> Hi thanks for feedback,
>
> I agree that putting everything in Component.onCompleted would be
> worse workaround
> than changing order but more explicit. On th
Hi thanks for feedback,
I agree that putting everything in Component.onCompleted would be
worse workaround
than changing order but more explicit. On the other hand it is a lot
less declarative.
In my application I build different kinds of settings using list of objects or
strings. I encountered t
I can see your point. But tmp1 is not changing during the first property init, so it won't be evaluated. The way to work around this order-specifc init is to do it explicitly in a Component.onCompleted
Sent: Wednesday, March 07, 2018 at 4:25 AM
From: "Tomasz Olszak"
To: development@qt-project.o
On 6 March 2018 at 14:06, Kevin Kofler wrote:
> Mitch Curtis wrote:
> > https://codereview.qt-project.org/#/c/221758/ makes
> > QObject::dumpObjectTree() and QObject::dumpObjectInfo() invokable so that
> > they can be used from QML.
>
> Would this have any security impact? I'm thinking of issues
Mitch Curtis wrote:
> I was hoping someone else would answer this because I have no idea what
> ASLR bypass is
ASLR bypass is when malicious code can find out addresses that it should not
know due to address space layout randomization.
Kevin Kofler
__
Hello,
I'm writing here because I don't know if it is a bug or intended behavior
and I should look more carefully in docs (haven't found anything mentioning
it yet).
Please consider 2 examples (can be pasted anywhere - you will see logs from
object initialization):
Item {
property int tmp0: g
