Cascades Development

[simon_hain]

In my c++ code i have a QList<MyClass>

In QML i want to show a number of containers that contain information about the particular MyClass, like name.

The list is accessible with a getter from Class2

I use

qml->setContextProperty("class2", class2);

to publish the c++ Class2 (extends QObject) to qml.

To get the list i define a getter with Q_INVOKABLE in the class:

Q_INVOKABLE
QList<MyClass> getMyClasses();

In QML i call it like this:

onCreationCompleted: showMyClasses();
function showMyClasses() {
  var myClasses= class2.getMyClasses();
  console.log("myClasses size: " + myClasses.size());
  for (var i = 0; i < myClasses.size(); i ++) {
     //do stuff
  }
}

But i get:

TypeError: Result of expression 'myClasses' [undefined] is not an object.

Is this approach systematically flawed? Or do i just do something wrong?

[kanaksony]

Hi Simon,

I guess you need to register your MyClass to expose it to QML.

https://developer.blackberry.com/cascades/documentation/dev/integrating_cpp_qml/index.html

http://doc.qt.digia.com/qt/qtbinding.html

qmlRegisterType<ImageViewer>("MyClass", 1, 0, "MyClass");

[simon_hain]

i did that by using setContextProperty, which is the other way of doing it.

[simon_hain]

It seems that QList is not supported as a datatype, and i also have to register my custom class, trying to figure out how to connect the dots given by http://doc.qt.digia.com/qt/qtbinding.html#supported-data-types now

edit:

resolved the QObject issue.

Now i get this problem:

I use

qmlRegisterType<MyClass>("com.isec7.materials", 1, 0, "MyClass");

 And in the qml

import com.isec7.materials 1.0

 And get an error:

arning: bb::cascades::QmlDocument: error when loading QML from: ...

module "com.isec7.materials" is not installed
    import com.isec7.materials 1.0

[MSohm]

Just a few points to confirm:

• You see that error when running on the device/simulator (custom components aren't supported in the preview window yet).
• You register before pushing your QML with the import?
• This is all happening in the same application.

[simon_hain]

- yes, i get the error on the actual device (preview is working fine, only displaying an error about the module)
- yes, i register the type after creating the main qml, and before calling createRootObject and setScene
- yes, all within one application

[MSohm]

You need to register the type before creating the main qml.  Switch those steps around and you should be good to go.

[PBernhardt · Accepted solution]

Actually, you need to register your custom component before you even create the QML file.

[simon_hain]

This was the thing i overlooked, thanks a lot Paul.

I decided not to go this way though, as i have ~100 bean objects and i don't want to convert them all to QObject, make all their properties accessible using Q_PROPERTY etc, this looks like awfully lot of work.

Instead my idea was to let the component fill itself from c++ by calling a Q_INVOKABLE function, in this function find the element and flll it. It's not working though:
http://supportforums.blackberry.com/t5/Cascades-Development/Find-a-dynamically-created-element-from-...