Hello,
It seems your App.result is not a js object, but a c++ object derived
from QObject.
Is it?
On 5/28/2021 10:24 PM, Jason H wrote:
I've got a really weird error:
qml: type: object [DEBUG-12344567890,N]
qrc:/screens/Result.qml:32: TypeError: Type error
The statements are:
console.log("t
Hello,
On 6/10/2021 2:11 PM, Tony Rietwyk wrote:
What file is the Warning at the top referring to? My bet would be
utils.h or utils.cpp?
Does this problem ever occur for this large project without the
warning appearing?
Yes.
If the problem tends to occur with files that have just been
On 6/12/2021 1:29 PM, Nicholas Yue wrote:
I have now moved the code into a small UI test app so there is already a
Qt loop in the main app but it stopped working (status code not printed
out) again, do I have to retain the app.exec() and app.exit() ?
Probably because your networkManager goes
I figured it out,
QNetworkAccessManager networkManager;
needs to be a member of the class (not within the doSubmit() method),
otherwise it would have gone out of scope before the reply returns
Cheers
On Sat, 12 Jun 2021 at 10:29, Nicholas Yue wrote:
> I have now moved the code int
I have now moved the code into a small UI test app so there is already a Qt
loop in the main app but it stopped working (status code not printed out)
again, do I have to retain the app.exec() and app.exit() ?
```
#include "GForm.h"
#include "ui_form.h"
#include
#include
#include
#include
