QML and Qt Quick

MouseArea is not suitable for multitouch. They only handle mouse events. Try "MultiPointTouchArea":http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-multipointtoucharea.html for touch events. There is also "TouchArea":http://qt.gitorious.org/qt-labs/qml-toucharea/ for Quick1

this doesn't work for me. The program didn't find the file. Perhaps this is because of my mac system. But in Qt Creator this is an error, too.

weiyuemin: That worked. thanks!

Thanks maxus for posting your find! It makes sense now.

Put your javascript logic that populates your controls in the QML source or pass the QML item reference (id) over to your javascript librarys functions as an argument?

Too bad there is no childAt() method in QML.

Thank you, @moeg687 ! This helped a lot.

Yep, one more time I forget to include the Q_OBJECT macro - IDE code generation is spoiling me.

I would say, don't allow to return from you editor until the user has given a valid input. That's not the job of the model to check that.

Hi all! I got some additional information regarding my problem. When I try to start the application (Ctrl+R) instead of debugging it (F5) I basically see the same error from the application output: @/home/root/firstqml: symbol lookup error: /home/root/firstqml: undefined symbol: _ZN28QDeclarativeDebuggingEnablerC1Ev@ As it makes no difference if I use the Release or the Debug build configuration I think it is a fundamental problem with the Run/Deployment options and not a debugging issue in fact?!

Thanks. I have another question. Instead of the images being loaded from a folder can I have the images come from a .js

Yes,it solved my problem.Thanks!

I just wanted to inform you guys about the solution to my problem. In summary, the problem seemed to be a C++ / QML-engine interfacing and memory management issue: I was lucky enough to identify a small set of candidate revisions of the software which potentially caused the described behavior. In these changes, there was noticeable that in the QML/Javascript code there was a lot of manual fiddling with list models. For example, specific list-model entries (provided by the C++ core) were accessed via ListModel.get(), and they were in turn stored as static property values. I assumed that this is dangerous because as soon as the C++ core deletes the list model entries, it is not guaranteed that the references stored within the QML engine are properly cleared. Therefore, I modified this part of the implementation, and suddenly the application was running perfectly stable again.

The DropArea component uses the QQuickDropEvent class which does not give access to mime data like the QDropEvent class does. Why don't you try creating your own custom qml component and override the dropEvent function which uses the QDropEvent class. That way you would have access to the file path.

Yes you can. @ MouseArea { id: mousearea11 x: 56 y: 51 width: 118 height: 110 anchors { fill:parent; rightMargin: 502; bottomMargin: 286; leftMargin: 56; topMargin: 51 } onClicked: { mainLoader.source = "load_images.qml"; page.state = 'State1'; } } @

I'm not quite following you here - so do you want to simultaneously display data from A, B, and C? Isn't that going to mean having separate QML root contexts anyways? Do you want to display them all in the same root context, but at different times in the program's execution? In that case, can you unbind and rebind data A, B, and C from the root context?