http://qt-project.org/doc/qt-5/qml-qtquick-workerscript.html#restrictions

Maybe you just didn't notice the restrictions part (ie script cannot access 
properties, methods or other attributes of the qml item etc).
Hard to say without seeing your workerscript implementation.

re, Jonni

________________________________
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org] 
on behalf of Matthias Barmeier [barme...@barmeier.com]
Sent: Tuesday, May 13, 2014 2:57 PM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] QML creates a Segfault

OK, its just a bit weird that the same program works without a WorkerScript.
The WorkerScript is just to make the gui more repsonsive it has no relevance to 
the function.

Thanks.

Am 13.05.2014 13:31, schrieb Juha Kallioinen:
On 13.05.2014 14:00, Matthias Barmeier wrote:
Hi,

when trying to download data in a WorkerScript thread I got this:


bash: line 1: 1459 Segmentation fault QT_NO_JOURNALD_LOG=1 DISPLAY=:0.0 
/usr/bin/CalDav

Can somebody explain if I can avoid this or what the reason is ?


That script part is  how Qt Creator runs your application in the 
device/emulator. So it just means that /usr/bin/CalDav crashed to a SEGFAULT 
and you'll need to figure out why.

Qt Creator launches the application in the device/emulator almost like this:

ssh nemo@device_address "QT_NO_JOURNALD_LOG=1 DISPLAY=:0.0 
/usr/bin/applicationname"

It does not use ssh command, but an ssh library, which is part of Qt Creator.

The QT_NO_JOURNALD_LOG =1 is there to make the application not put its output 
to journald, but to stdout/stderr instead so that Qt Creator can display it.

Best regards,
 Juha




_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org<mailto:devel-unsubscr...@lists.sailfishos.org>

_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Reply via email to