QML and Qt Quick

This thread is continued "here":http://qt-project.org/forums/viewthread/17435/.

First thing, have you seen my post to your "other thread":http://qt-project.org/forums/viewthread/17391/? Also if you are targeting Symbian Belle i would suggest you update through Qt Creator packet manager to get the Symbian Belle toolchain (i will guest you have Symbian Anna toolchain). Next be sure to copy the correct binary version of QZXing to the correct folder. Finally the most important thing, donwload the latest version of the library files. I just figured out from your other post that you have downloaded the library from a repository that is outdated (https://github.com/zxing/zxing). The correct repositories you have to take a look at are: The "QZXing's project page":https://projects.developer.nokia.com/QZXing/browser The official and most up to date "ZXing site":http://code.google.com/p/zxing/source/checkout . In there under the folder Symbian you will find QZXing once again (The first option is recommended since you won't have to download other unnecessary files. ) So do all the updates, try it once again and get back to us with the result.

You didnot have to go through that much trouble. There seems to be a problem with the path variable. make sure that you have given it correctly and that all the extensions are separated by ";". Hope it helps

Hmm, I think you're right. I never thought it wouldn't work because I've been able to return the value on web projects for example. I tried this on my MainPage.qml: @Component.onCompleted: console.log(Database._Load_ColorTheme())@ And guess what... It gives me 'undefined'! So how I'm supposed to do this then? I got an idea, that I could use 'Label' or 'Text' components, and load the new color from a 'text' variable. But after all, this should work like a Javascript in any other situation, right .. ? So what's going wrong here?

Yes, the assignment form in your first post won't cause a binding. In QtQuick 1.x you can use a Binding element, and in QtQuick 2.0 you can either use a Binding element, or use the "initial property values" argument to the setSource function of the Loader, along with the Qt.binding() function, to generate a binding.

Thanx sooooooooooooooooooo much I solved by your help of course

So, to have an inside radius, you'll have to make radius bigger than the border width. If this solves your question, could you please edit your first post and add [solved] to it? Thanks.

I tried using a "QML loader":http://doc.qt.nokia.com/4.7-snapshot/qml-loader.html instead of calling setSource from C++ but that also leaks.

You could use Repeater for each set of GridView 3x3

Thanks for your suggestion. I replace QQuickPaintedItem with QQuickItem and solve the performance issue now. And I found VideoOutput in QtMultimedia is a good solution, too.

For those who can be interested in that, I've resolved, but not in a elegant way! In myListView I've created a qml ListModel attached to ListView and then thru javascript functions they manipulate ListModel. But important, you cannot pass from within C++ to qml a flat QList<QObject*> because itsn't supported well, instead you need to pass the QList thru setContextProperty of QDecalarativeContext to use in qml Bye

Sorry...i forgot it!

Well, does anybody have a working files, that really works, could anybody leave working example here? ... documentation is quite mean on that...

First I thought it is possible but it seems that header or footer element id is not recognized properly. Here's the modified code that worked for me. Main point is using a universal scoped variable @import QtQuick 1.1 import com.nokia.symbian 1.1 Page { property string buttonText : "OK" ListView { id: list_view1 anchors.fill: parent delegate: Item { x: 5 height: 40 Row { id: row1 spacing: 10 Rectangle { width: 40 height: 40 color: colorCode } Text { text: name anchors.verticalCenter: parent.verticalCenter font.bold: true color: "white" } Button { id: button1 x: 272 y: 0 text: "Button" onClicked : buttonText = model.name } } } model: ListModel { ListElement { name: "Grey" colorCode: "grey" } ListElement { name: "Red" colorCode: "red" } } header: ToolButton { id : button text: buttonText } Button { id: button1x x: 272 y: 0 text: "Button" onClicked: buttonText = "It works" } } } @

Implement a custom declarative item, reimplement event() and handle the touch events. This item can then have some signals to indicate a touch event has occured and a number of properties that provide the touch point data (position, etc.). This is exactly what QQuickMultiPointTouchArea (the implementation of MultiPointTouchArea) does in Qt 5. Alternatively, if a custom item is not desired, you could still install an event filter on the declarative view and expose the events/data to QML via a QObject.

I have pushed it as a bug [QTBUG 25999]...

Hi all, Search for some posts - there is a specific bug in PositionSource which causes your device to look for GPS data and hanging up on it if no GPS signal is received (hence you see GPS icon). This means outside your code will work fine, but PositionSource won't automatically look for non-GPS sources... Best workaround is to go with Qt C++ and write custom nonGPS PositionSource. Problem will be again if you rely on GPS more - to code something to manage "blending" different sources...

Hi Chris, Thank you too much because of your reply. I did solve this typing: @ children:[ Text{ id:textDate anchors.centerIn: parent }, CommonHeader{ searchActive: false section: qsTr("MI CIUDAD") z:100 } ] @ instance of doing by default property. I don't know why it solved the problem. But I understood that you told me almost everything. I'm not sure from where it is accessing to the component. But doing explicit code, it doesn't happen. Best, Fernando.

You probably want to use http://qt.gitorious.org/qt-components/desktop on desktop.

I'm not 100% certain, but I seem to recall someone saying that transform with QGV is much slower than with scenegraph rendering (ie, Qt 4.8 will be slower than Qt 5.0, in that QtQuick 1.1 will be slower than QtQuick 2.0, for transform operations) - although I can't remember why, now. Perhaps scenegraph allows partial-update and thus only the transformed element needs to be redrawn? Not sure.