On Thursday 04 September 2014 11:57:33 Mike Nolan wrote: > I cannot understand why this is, however. Is this a bug in > QDeclarativeDebugServer or am I maybe breaking a rule about using > qInstallMsgHandler? I have a slightly better workaround (always printing > if the QML file hasnt loaded yet) but Id like to understand this better.
It's a bug in QDeclarativeDebugServer that it relies on qDebug to communicate with Creator. Or it's a bug in Qt Creator that it expects a debugging message from QDeclarativeDebugServer. Please upgrade your Qt Creator first to 3.1 and then try again. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
