Souds like they are getting a Promise result from the framework and are not
"await"ing for it.
> Sent: Saturday, December 15, 2018 at 3:35 PM
> From: "Roland Hughes"
> To: "Jason H"
> Cc: interest@qt-project.org
> Subject: Re: [Interest] restu
Turns out the problem wasn't mine. Previously we had been using
websockets but now websockets are bad so went with Web channel. Honestly
believed the bug was mine since the captive Web site worked fine with
websocket previously. Turns out it wasn't. Latest "front end" code has
html, angular, ja
I did this, in some abandoned work. Turns out QWebWhatever didn't do it right
on iOS. It can't return a QVariantMap, you have to stringify it.
Timer {
id: testTimer
interval: 1000
repeat:false
running: false
onTrigger
