@hemang_1711 I have just gone back to your original post and I see again what originally confused me.

If you recall, I asked about GraphParam, which you are trying to access in your QML. I looked for this in your model implementation, but your model does not have a role "GraphParam".

You do have a role "GraphList", which seems to return the first element of the list member named GraphParam in the GraphModelItem struct in your implementation. Although GraphParam is the name of the struct member, QML does not know anything about this name. It only sees the names you have defined in your roles.

@ECEC said in Binding C++ objects in std::vector to QML components:

@jeremy_k

I'm not too sure what benefit you are suggesting QStandardItemModel would have over subclassing QAbstractListModel.

The only advantage is less stuff to write and maintain. I count 6 lines of code above, including headers, specific to the standard item model.

Use a SequentialAnimation and put a PauseAnimation in it first, with a duration depending on the index of the delegate.

@Kyeiv
https://doc.qt.io/qt-5/qtquick-modelviewsdata-modelview.html#models

those are your possibilities

@LeLev Many thanks!

@raven-worx thanks. it works.!
Thank you all for ur supports.

Hereby a solution that works for me. Instead of using a repeater, this codesample works with the ChartView's onCompleted signal handler. In the onCompleted handler first three LineSeries are dynamically created, then an AreaSeries is created.

ChartView { id: chartid anchors.fill: parent antialiasing: true //Valueaxis ValueAxis{ id:xAxis; min: 0; max: 40000; tickCount: 9 } ValueAxis{ id:yAxis; min: -200; max: 1400; tickCount: 17 } //Listmodel only for testing Area- and LineSeries concept ListModel{ id: listModel ListElement { x1: 18000; y1: -100; x2: 18000 ; y2: 400 } ListElement { x1: 25000; y1: -100; x2: 25000 ; y2: 1000 } ListElement { x1: 31000; y1: -100; x2: 31000 ; y2: 1200 } ListElement { x1: 36500; y1: -100; x2: 39700 ; y2: 1250 } } Component.onCompleted: { var count = listModel.count; for(var i = 0;i < count;i ++) { if (i < count - 1) // add LineSeries { var lineTypeSeries = chartid.createSeries(ChartView.SeriesTypeLine, "line" + i, xAxis, yAxis); lineTypeSeries.color = "black"; lineTypeSeries.width = 2; lineTypeSeries.borderWidth = 0; lineTypeSeries.append(listModel.get(i).x1, listModel.get(i).y1); lineTypeSeries.append(listModel.get(i).x2, listModel.get(i).y2); } else { var areaTypeSeries = chartid.createSeries(ChartView.SeriesTypeArea, "area" + i, xAxis, yAxis); areaTypeSeries.pointsVisible = true; areaTypeSeries.color = "lightgrey"; areaTypeSeries.borderColor = "black"; areaTypeSeries.borderWidth = 2; areaTypeSeries.lowerSeries = chartid.createSeries(ChartView.SeriesTypeLine, "lowerSerie"); areaTypeSeries.lowerSeries.width = 0; areaTypeSeries.lowerSeries.borderWidth = 0; areaTypeSeries.lowerSeries.color = areaTypeSeries.borderColor; areaTypeSeries.lowerSeries.capStyle = 0x00; areaTypeSeries.lowerSeries.append(listModel.get(i).x1, listModel.get(i).y1); areaTypeSeries.lowerSeries.append(listModel.get(i).x2, listModel.get(i).y1); areaTypeSeries.upperSeries.append(listModel.get(i).x1, listModel.get(i).y2); areaTypeSeries.upperSeries.append(listModel.get(i).x2, listModel.get(i).y2); } } } }

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?