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 [email protected] http://lists.qt-project.org/mailman/listinfo/development
