QML and Qt Quick

@p3c0 Yep, it works! I had to test this case before creating new thread. Anyway, thanks! I'll open an issue on GitHub.

Thanks @p3c0 Based on the documentation, QtDeclarative has already been deprecated in favor of the two new classes: Qt Quick and Qt QML. QQuickPaintedItem can be use as convenient way to port QDeclarativeItem-based classes that use the QPainter API. I've been searching on the internet how to render text on QSG nodes but to no avail. I'm still stuck into this problem. :(

@p3c0 it does yet I wanted to fix the problem I personally faced thanks for an advice

@silex92 Perhaps you should post some code to try the scenario.

The problem is actual for QT version 5.4

Thank you for your answer! I found even more simple solution - check QQuickItem::childAt for null. If it isn't null then I call inherited QQuickView::mousePressEvent method, otherwise I do my own work

@p3c0 Thanks a lot.

@belab Found it:var rs = tx.executeSql('SELECT rowid, * FROM Cards');

You could also try to use your C++ object as a prototype: QJSValue myType = engine->evaluate("function MyType() {}"); myType.setPrototype( engine->newQObject(new MyTypeCpp)); I've not tried this, but this could work. Probably you would to have to set myType as property in the JSEngine::globalObject().

@Dmitriy You're welcome :) Good luck!

Thanks Wieland, Yeah so the asynchronous object creation is possible for both. The only major difference which I could find by studying the doc was that the instantiated qml component is destroyed when the Loader's source property is changed but you have complete control of the lifetime of the qml component when you explicitly manage the lifetime via javascript.

import QtQuick 2.4 import QtQuick.Window 2.2 import QtQuick.Controls 1.3 Window { visible: true width: 400 height: 200 TextArea { id: chat anchors.fill: parent property int threshold: 10 text: "Current\ntext\n\\to\nmove\ndown\ndown\ndown \ndown\ndown\ndown\ndown\ndown\ndown\ndown" Component.onCompleted: cursorPosition = text.length flickableItem.onContentYChanged: { if(flickableItem.contentY <= threshold) { var oldHeight = flickableItem.contentHeight text = "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua." + text flickableItem.contentY = threshold + flickableItem.contentHeight - oldHeight // leave flickable in old position } } } }

@Chris-Kawa Thanks. Btw, is there a way to make something OO like in qml? I mean from my point of view I have a bunch of objects with different properties, some of then even contain another such objects. And I'd want to be able to draw all of them with these properties but all delegate/role models imply that I have some common set of properties which is not the case. Isn't there a way to "bind" some c++ qt object to it's proper qml representation stating how it should be drawn? For example, If I have object with int foo and QString bar property I'd like it to be drawn as Rectangle with foo and bar displayed inside of it. And if I have object wich is a "node" i'd like to draw it as the on above but with all children to the right or inside.