Hi,
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. Simon ________________________________ From: Thiago Macieira <[email protected]> Sent: Monday, September 26, 2016 8:14:58 PM To: [email protected] 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: https://codereview.qt-project.org/170491 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
