Could it be related how and where the qml is loaded? I'm reading the
qml files from resource file. I haven't tested this yet with simple
application that uses the default sailfishapp structure, so that I
could confirm this, just guessing.
--
Tero
2014-02-24 9:00 GMT+02:00 Andrey Kozhevnikov :
>
working fine for both cpp and qml output
On 24.02.2014 05:37, Artem Marchenko wrote:
I found message handler working just fine (both for QML console and
cpp qDebug() messages) is emulator builds, but not for when code is
running on device. Go figure.
Could it be so that on device exactly QML
Hi
This may be related:
I haven noticed that using journalctl to view system logs on the
device, QML and C++ debug output is reported differently.
Below is an example extract:
C++ debug is reported with the application name.
QML debug is reported as lipstick
Feb 23 13:39:39 localhost lips
I found message handler working just fine (both for QML console and cpp
qDebug() messages) is emulator builds, but not for when code is running on
device. Go figure.
Could it be so that on device exactly QML engine is somehow always used
separately from your c++ execution context.. no it doesn't m
On 04 Feb 2014, at 22:37, Tero Siironen wrote:
> Andrey Kozhevnikov kirjoitti 4.2.2014 kello 23.14:
>
>> This is messages handler i'm using in my projects:
>
>
> This doesn’t seem to make a difference for me, the log file still contains
> only c++ side debug prints, qml prints (like console.l
Andrey Kozhevnikov kirjoitti 4.2.2014 kello 23.14:
> This is messages handler i'm using in my projects:
This doesn’t seem to make a difference for me, the log file still contains only
c++ side debug prints, qml prints (like console.log()) are not handled with
messagehandler.
Actually I foun
This is messages handler i'm using in my projects:
void writeLog(const QString &type, const QMessageLogContext &context,
const QString &message)
{
QString time = QDateTime::currentDateTime().toString("hh:mm:ss");
QFile file(LOG_FILE);
if (file.open(QIODevice::Append | QIODevice::Tex
