Il 14/04/21 16:15, Jérôme Godbout ha scritto:
Yeah that would be a pain, but if it work you can try to reduce the
QVariant usage to a minimum from that point.
1. QVariantMap
2. QMap
3. QMap
4. QMap
5. QMap>
6. QMap>
See up to where you can reach before it fail, it will tell you which
da
M
To: qt qt
Subject: Re: [Interest] [EXTERNAL] Re: Send Data to JavaScript
On 12.04.2021 20:48, Jérôme Godbout wrote:
Have you tried with a QVariantMap for your Q_PROPERTY instead? Will be dull to
convert from QVAriant to list and string for each values, but will probably
work.
I've not
On 12.04.2021 20:48, Jérôme Godbout wrote:
Have you tried with a QVariantMap for your Q_PROPERTY instead? Will be
dull to convert from QVAriant to list and string for each values, but
will probably work.
I've not tried using that, but looking at it, wouldn't it mean
that
I'd have to co
On 12.04.2021 16:12, Giuseppe D'Angelo via Interest wrote:
But a similar consideration applies: do you have any documentation
telling you how datatypes in C++ are mapped to datatypes in JS -- and
thus if your QMap is supposed to be supported,
or if instead you need to "massage" it a bit?
T
Il 12/04/21 15:56, John Schneiderman ha scritto:
On 12.04.2021 15:35, Giuseppe D'Angelo via Interest wrote:
Are you sure about the transformation? Only certain data types are
supported for the C++ <-> QML data exchange, and I don't believe the
one you're using is:
I'm not using QML in this part
On 12.04.2021 15:35, Giuseppe D'Angelo via Interest wrote:
Are you sure about the transformation? Only certain data types are
supported for the C++ <-> QML data exchange, and I don't believe the
one you're using is:
I'm not using QML in this particular case. I'm using QWebEngine and
QWebChan
