QML and Qt Quick

Got the same problem and solved it by using renderType: Text.NativeRendering. Don't really know whether it's a bug or not.

The "z" value often works not in the way we mere mortals think about it :) This is mostly due to parent-child relationships of QObjects. Please verify whether moving the components about in the parent-child tree works or not (move your component declarations inside your QML file and see how it changes the behaviour and positioning).

It simple: tr is a method of QObject and main is a function not a QObject

Okay I have found: http://qt-project.org/doc/qt-5.0/qtqml/qtqml-cppintegration-definetypes.html#receiving-notifications-for-object-initialization This might probably work.

Sorry in advance for being concise, I don't have much time right now. Feel free to ask for clarification. You can probably separate the tabs into a simple ListView (just hack it so that it looks like tabs), and then load the content of a given tab with Loader (or use States if you prefer) I don't understand this bit, but I haven't read your post fully. Maybe I'll get back to this later. Just a hint: KDE project probably has some ready-made breadcrumb components. OK this is quite complicated territory. I advise going step by step, carefully reading the documentation (it's really good, but it's hard to wrap your head around some concepts). Start with a simple QStringList as a model (just to get a feel of how it works) and then slowly start adapting your code so that it can handle your data models.

I am using the latest, Qt 5.1.

[quote author="dasun" date="1382849565"]I'm not familiar with qt 4.x but I guess you can use "at function":http://harmattan-dev.nokia.com/docs/library/html/qt4/qdeclarativelistproperty.html#AtFunction-typedef directly inside qml as in qt 5.x.[/quote] That would work for a QList<QObject*>, but I'm working with a QDeclarativeListProperty. I now have this working. I think there was one error that I was facing that had to do with something unrelated to what I was trying to do here, but also I was informed "here":http://stackoverflow.com/questions/19503898/can-a-qdeclarativelistproperty-be-accessed-directly-instead-of-as-a-model that I needed to setup my context properties and registered types before loading my source URL. Once I rearranged my code to make that happen, everything did start to work. I don't know if that's a known issue or bug, and if the same goes for Qt 5.x.

Hi and welcome to devnet, Do you have @QT += qml@ in your pro file ?

That depends. QtQuick1 (called QtDeclarative in Qt5) module uses a raster engine, so it should work everywhere. QtQuick 2 requires OpenGL (there is no software rendering fallback here). But since we're in Beta, it may well be that you have discovered a bug :) I'm not experienced enough with Qt 5 on Android to say for sure.

@import QtQuick 2.1 import QtQuick.Controls 1.0 import QtQuick.Window 2.0 ApplicationWindow { title: qsTr("Hello World") id: mainWindow width: 640 height: 480 menuBar: MenuBar { Menu { title: qsTr("File") MenuItem { text: qsTr("Exit") onTriggered: Qt.quit(); } } Menu { title: qsTr("Help") MenuItem { text: qsTr("About...") onTriggered: aboutWin.show(); } } } Button { text: qsTr("Hello World") anchors.horizontalCenter: parent.horizontalCenter anchors.verticalCenter: parent.verticalCenter } Window { id: aboutWin; color: "black"; title: "About Me"; x: mainWindow.x + mainWindow.width/2 - width/2 y: mainWindow.y + mainWindow.height/2 - height/2 Rectangle { anchors.fill: parent anchors.margins: 10 Text { anchors.centerIn: parent text: "Glory Be!" } } } } @

You should even be able to have a complete empty ListModel; @ ListModel{ id: myListModel }@