QML and Qt Quick

The point is: to avoid this kind of error when parsing the QML file: @ video.qml:2:1: module “QtMultimediaKit” is not installed import QtMultimediaKit 1.1 @ you must have all necessaries files inside of "imports" directory of you PySide/PyQt installation.

@kathy only add "Solved" to the title of this post

A little late, but I had have a solution. I just had to correct my $QTDIR variable. After all, I had a similar problem on Ubuntu: I had have a qt path to opt/.. before my to QtSDK in my $PATH variable. After making the path to QtSDK and having a proper $QTDIR variable, it compiled like a charm, and the qt-components worked just fine :) (except the meego related stuff, because I haven't installed all the libraries for it)

What are you trying to say CMGeorge? Did you check your code? [quote author="CMGeorge" date="1305232932"]@Rectangle { id: dragthis x: 10 y: 80 color: "green" width: 50 height: 50 MouseArea { anchors.fill: parent drag.target: dragthis drag.axis = XandYAxis drag.active = true } }@[/quote]

And your .qml file works in the QML Viewer without problems?

awesome, it works like a charm.

I tried to verify this as far as i could. In fact there is some kind of scope problem. In my main Qml object lets call it "FirstLayer" I'm call on the Component.onCompleted signal a javscript function which builds me different Qml objects using the Qt.createComponent() and component.createObject() functions. After this is finisched the "FirstLayer" object has two "Screen" objects and each "Screen" has at least four "Button" objects. The build process stores all the child objects like "Screen" and "Button" in the corresponding global javascript arrays. In the context of the "FirstLayer" I can access these arrays perfectly. But although I declare the .js file which contains the array as .pragma library I didn't access the same arrays within the context of the "Screen" or "Button" objects. In their context these arrays are still empty. So it looks like they are initializing there own instances of these arrays. And I have no idea how to solve this. So if anybody has an idea how I can fix that. Please let me know. Thanks for any help guys.

Try with 'myRec.children.length'

Please report if it worked for you kuba. I've got the same issue with the desktop-components, but was too lazy to do anything about it. So I wrote all QML by hand until now.

In Qt Quick 1.1 you can establish binding in imperative JS code... See http://developer.qt.nokia.com/forums/viewthread/5494/

Did you try this in SampleModel.qml : @ import QtQuick 1.0 ListModel { ModelElement {url: myfunction(input) }, ModelElement {url: myfunction(input) }, ModelElement {url: myfunction(input) }, ModelElement {url: myfunction(input) } } @ But I think you should not store a function in the modelelements, just store values and when needed update the value in the model.

Hi, We have implemented something similar to this (without the drag + drop). Our solution is to store the folder structure as a C++ list model, with items being inserted/deleted when the view opens or closes a folder. Using roles for the items allows the QML to know whether the item has children and if it's open. This breaks the model/view structure in that the underlying model knows which folders are open in the view, but it means the QML is nice and simple. Regards, Steve

Yes it does, I've just commented out the check and the warning appears.

ok thanks. I used another approach to realize this.

it's done, I used this link as reference: "http://doc.qt.nokia.com/4.7-snapshot/qtbinding.html":

I am really interested to see how dragging an element from one container to another is done.

Hi, Ok, it's not a problem with QML. I was trying to catch linkClicked(QUrl) signal from QWebView in C++, and pass them to QML. By default QUrl encloses urls in double quotes while converting them to strings ( when I call toString() ). Thanks for your reply !!!

I actually tried connecting to a 'onCountChanged' signal on the ListModel but w/o success. Don't know if that is a bug or feature :)

I seem to have found my problem. Apparently if I change the "import QmlProject 1.0" in the *.qmlproject file to "import QmlProject 1.1" everything works just fine. I think this might be a side effect of creating the project in the Qt SDK 1.1 (with creator 2.1) and then working with it in Creator 2.2 or something.