As it happens, I can live without QML debugging, I'm hunting issues in C++ anyway. Disabling QML debugging did the trick, thanks!
I'm on Linux, plus what I'm doing is rather compute heavy, so running on a device is something I try to avoid at this point. Harri On 07/02/2012 09:51 AM, [email protected] wrote: > The "Arrow with the bug in it" starts the application inside the Debugger. > Unfortunately enabling QML debugging (checkbox in Run Settings of your > project) breaks some Symbian components, so this is a known issue :( You can > either decide to live with the effects, or disable QML debugging. > > (The technical reason is that the QML Debugger in Qt 4.x runs it's own event > loop inside the GUI event loop. This however can change the order of events > being delivered to the application, which somehow breaks the components. This > has been fixed in Qt 5.0 by moving the QML debugger into it's own thread, but > that of course doesn't help for the Symbian case). > > Hoe this helps, > > Kai > > PS: I'm not sure whether it makes a difference whether you let your > application run in the Simulator or on the device. > > ________________________________________ > From: [email protected] > [[email protected]] on behalf of ext > Harri Pasanen [[email protected]] > Sent: Thursday, June 28, 2012 5:54 PM > To: [email protected] > Subject: [Qt-creator] Strange difference when running with debug, as > opposed to just running > > I have some code that runs ok in Qt Simulator when launched from Qt > Creator by clicking on the green arrow head. > > But if I run it clicking the arrow head with a bug on it, I see > messages like > > file:///home/harri/QtSDK/Simulator/Qt/gcc/imports/com/nokia/symbian.1.1/ContextMenu.qml:89: > Unable to assign QObject* to Popup_QMLTYPE_18* > > file:///home/harri/QtSDK/Simulator/Qt/gcc/imports/com/nokia/symbian.1.1/MenuContent.qml:64: > TypeError: Result of expression 'containingPopup' [null] is not an object. > > > and when the application comes up, the toolbar (ToolBarLayout) is empty, > without any buttons. > > Similarly, running with valgrind memcheck, the toolbar is populated ok, > and none of the above errors appear. > > I'm not sure exactly at what moment this started happening, might have > been back when added the toolbar, as previous revision did not have > any. I don't run the debugger so often, so I did not notice until now. > > I don't have any breakpoints set. > > Kind of strange, any ideas? > > /Harri > > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
