[Development] Behaviour change in QML in Qt 5.8 regarding null

[Chris Adams]

I'm certain that it's possible.  I suspect the reason why the code used
QVariant is that when it was originally written (in Qt 4.7 days, IIRC),
QJSValue didn't exist, and it simply hasn't been ported to newer interfaces
since then.  Without knowing too much about the QML bindings in QtPIM, I am
going to assume that there is at least some effort required to port all of
the usages and update all of the unit tests.

On Thu, Sep 29, 2016 at 1:50 AM, Thiago Macieira <thiago.macieira at intel.com>
wrote:

> On quarta-feira, 28 de setembro de 2016 15:42:06 PDT Simon Hausmann wrote:
> > I don't think the QVariant interface is deprecated, but it just
> inherently
> > unsuitable for JavaScript specific things such as distinguishing
> undefined
> > from null or storing function closures. That is why the engine supports
> > both, for different purposes.
>
> Chris, is it possible to use the QJSValue interface instead? Why did the
> code
> use QVariant?
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160929/0404e5f7/attachment.html>