ToolBar buttons aren't visible while running debug on Simulator

Hi all!

Strange behavior of Simulator while running Debug of my QML project with PageStackWindow - ToolBar buttons are not displayed at all.

If running without debugging (I mean simple run with Ctrl+R) then ToolBar buttons are visible.

Is there any way to fix this?

Thanks!

PS: latest Nokia QtSDK.

Hi

I have checked on the latest Qt SDK 1.2.1 . ToolBar buttons are shown.

Please check you enable it
[CODE]
PageStackWindow {
...........
showStatusBar: true
showToolBar: true
..........
}
[/CODE]

Also there is useful QML component gallery application project that can serve you as code example : [URL="https://projects.developer.nokia.com/uivisualisation"]https://projects.developer.nokia.com/uivisualisation[/URL]

Checked, they are enabled.

When I run project with simple "green play button" (Ctrl+R) then ToolBar buttons are visible, but when run it with "green play button with bug" then there no buttons on toolbar at all.

Hi

indeed Simulator Qt for MinGW in debug mode gives property binding error that prevents toolbar instantiation : [CODE]file:///C:/QtSDK/Simulator/Qt/mingw/imports/com/nokia/symbian.1.1/PageStackWindow.qml:86: Unable to assign QObject* to ToolBar_QMLTYPE_1*[/CODE]

I have created [URL="https://bugreports.qt-project.org/browse/QTCREATORBUG-7634"] QTCREATORBUG-7634 bug report on that[/URL]

Thanks for creating a bug report, but it already closed with such comment:
[QUOTE]Kai Köhne added a comment - 16/Jul/12 11:38 AM
This is a known issue: The QML debugger in Qt 4.x uses QEventLoop's to be able to process events from the network when being stopped. However, this means that the order of delivery for all events might be altered, which breaks the Symbian components. The problem underneath has been fixed in Qt 5, but there's no way to solve the fundamental issue in Qt 4 (except maybe for working around it in the Symbian components, which are AFAIK done). So I'm afraid you have to disable "QML debugging" in the run settings when debugging, or ignore the error.
[/QUOTE]

It is unfortunate that the problem will remain without a solution.

Yes I have seen that resolution. In fact there are extremely few cases when you need debug --- console.log is enough to understand problem i think.

In most cases. But sometimes it is necessary to debug a cpp code, but in the same time a navigation buttons on the toolbar is not available. It's not so critical but uncomfortable.

Thanks for support, Igor.