+0200
Subject: RE: [Qt-qml] C++ Data Models and plugin mechanism
QDeclarativeExpression: Expression (function() { return
myPluggedInObj.myModel }) depends on non-NOTIFYable properties:
This message means that one of the properties in the expression does not have
a NOTIFY signal, so
:57 +0200
Subject: RE: [Qt-qml] C++ Data Models and plugin mechanism
So you can only extend QML Data Model by reimplementing
QDeclarativeView. Am I correct?
Fortunately not. setContextProperty is just ONE way of creating an identified
object.
To make a model as a type in a plugin
QDeclarativeExpression: Expression (function() { return
myPluggedInObj.myModel }) depends on non-NOTIFYable properties:
This message means that one of the properties in the expression does not have a
NOTIFY signal, so if it changes, the expression will not be re-evaluated, so
this:
Hello,
I am enjoying QML. I wanted to confirm what I have been researching. Right now
as it stands, if you want to extend a QML Data Model in C++ (as in the C++ Data
Models section
in http://doc.qt.nokia.com/4.7-snapshot/qdeclarativemodels.html#C++). You can't
do that with a plugin (similar
So you can only extend QML Data Model by reimplementing
QDeclarativeView. Am I correct?
Fortunately not. setContextProperty is just ONE way of creating an identified
object.
To make a model as a type in a plugin, just inherit your type from
QAbstractItemModel (rather than QDeclarativeItem as
On 18/05/2010, at 6:41 AM, ext Bartosh Wroblevksy wrote:
I am enjoying QML. I wanted to confirm what I have been researching. Right
now as it stands, if you want to extend a QML Data Model in C++ (as in the
C++ Data Models section in
