QML and Qt Quick

Note that the "valueChanged" function is a function property of "obj" and not of the "value" property of "obj". So, instead of: @ obj.value.valueChanged.connect(objEventHandler) @ you should use @ obj.valueChanged.connect(objEventHandler) @ Depending on the situation, using a declarative Connections element is better, though (for example, if the target of the dynamic connection can change depending on the situation). In some situations, on the other hand, using an imperative connection can be better (as you don't incur the overhead of constructing an extra QObject). Cheers, Chris.

You can alsouse the new Canvas item which essentially gives you QPainter functionality in javascript.

It seems QAction is something specific for QtWidgets. A solution is to override @void keyPressEvent(QKeyEvent* event);@

Creating a plug-in (aka module) allows you to easily re-use your components. The base class, use "QQuickPaintedItem":http://qt-project.org/doc/qt-5.0/qtquick/qquickpainteditem.html. Override the "QQuickPaintedItem::paint":http://qt-project.org/doc/qt-5.0/qtquick/qquickpainteditem.html#paint. You can draw text with the "painter->drawText":http://qt-project.org/doc/qt-5.0/qtgui/qpainter.html#drawText

Thank you very much Thomas. That sure did the trick. You rock!

[quote author="frederik" date="1360885598"]The dev branch requires Qt 5.1 (the dev branch of all Qt repos).[/quote] Thanks for the information. I will waiting the Qt 5.1 release, and I will use in my projects the stable branch of repository.

Visible should hide the list. If it is not the case it would be best to create a small self-contained example of this behavior and file an issue at https://bugreports.qt-project.org

I have solved this problem using function pointer. It is not the best solution but it works finally.

This is how QML works. Every component you declare is a separate instance. You could experiment with transforming your class into a singleton, or you can instantiate the component in C++ and passing instances to GUI, or maybe a clever use of Loader could help: @ MyCamera { id: globalCamObject } Loader { id: camera1 sourceComponent: globalCamObject } Loader { id: camera2 sourceComponent: globalCamObject } @

[quote author="z.emb" date="1360759775"]http://qt-project.org/forums/viewthread/21396/#114311 doesn't help you at all? In my thread mentioned above is also a link to the "Ogre":http://qt.gitorious.org/qt-labs/qmlogre implementation which does basically the same thing.[/quote] Thank you, it helped me, but... not enough.

Hi mbrier, Did you tried QQuickView::setResizeMode(QQuickView::SizeRootObjectToView) in your main program. It takes care of the resolution in a better way. Regards Ansif

Good luck!!!!!!!!!

Guys I have been just told that I need to use the version of the compiler that will be compatible with both Windows and Linux, which is MinGW but 4.4 version, the one I've started using at the beginning. Please help me guys.

Qt and/or QML is not using Java.

When I said QmlViewer I meant the Qt qmlviewer.exe. So you solved my problem. The thing is, is have an application which loads n instances of the qml viewer as an DLL. My QtQuick item has an static List which collects the pointers of all created elements of this type. And with the QGraphicsItem::scene () mehod I can find out, which elements are on the same qml viewer page. :)