Ok, it looks like a bug introduced since Qt 5.8. I filed a bug report: https://bugreports.qt.io/browse/QTBUG-74332

@KillerSmath Its working! NOTIFY did the trick. The final touch that I also included was to use a Q_INVOKABLE getModuleAt(i) instead of a Q_INVOKABLE getTextBodyAt(i); this allowed me direct access to the DataModule's property: Text{ text: dataModel.getModuleAt(index).TextBody } portion of datamodule.h: class DataModule: public QObject { Q_OBJECT Q_PROPERTY(QString TextBody MEMBER textBody NOTIFY textBodyChanged) . . . signals: void newVal(DataPiece*); void textBodyChanged(QString newText); Q_INVOKABLE method inside of the QML context class datamodel.h: Q_INVOKABLE DataModule *getModuleAt(int i); Brilliant! Thanks for the help mate. Hopefully this is helpful to others as well.

Ok. Thank you for your answer. I never use QAbstractListModel. Do you have some keys to start ? What is difference between using QAbstractListModel and QQmlListProperty ? In which case is it better to use them ?

@Qmyo You can create a 2 Q_INVOKABLE functions. One will return the Repeater's model number and other will return ListView's models. You can make use of index attached property which can be passed to the Q_INVOKABLE functions to return particular model.

@dxmachina Well, that's not true ;) Just a little mistake. Happy coding! :D

Thanks for your reply.

Yeah, here you go: http://pastebin.com/7CZSCnsQ The problem is rep1. I figured it might be a bug in my Qt version and updated and now everything is broken and nothing will compile, so I can't give you a screenshot. But it's pretty much like in this fine paint art: http://imgur.com/jQHaAoL What I'm trying to show is that the 0. element is outside the the visible area, and if I resize it, it's still stuck to the bottom. Edit: I still have a backup of my system with the old version, so I could still roll back. But I want to wait, maybe someone can help me with the compiler errors first (other post).

Still looking for a solution to this, any ideas?