[Development] Behaviour change in QML in Qt 5.8 regarding null
Simon.Hausmann at qt.io
Tue Sep 27 13:25:49 CEST 2016
That is exactly the part I'm referring to. Receiving a QVariant from the QML engine and relying on it
to contain a specific type.
From: Thiago Macieira <thiago.macieira at intel.com>
Sent: Monday, September 26, 2016 8:14:58 PM
To: development at qt-project.org
Cc: Simon Hausmann
Subject: Re: [Development] Behaviour change in QML in Qt 5.8 regarding null
On segunda-feira, 26 de setembro de 2016 09:31:34 PDT Simon Hausmann wrote:
> That said, this is not quite the same as changing the return type of a typed
> C++ function. QVariant is designed
> to hold any type and if you receive a QVariant it has always been a little
> dangerous to rely on specific conversion
> behavior (throughout Qt).
Only if you didn't make the type part of your API, which is what QML had done.
See the failures:
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development