@Kyeiv said in ListView model from Q_PROPERTY problems: What am i doing wrong that the view is empty? The problem is that QList<QString>() is not a valid type for a QML model! QML model can be QList<QObject*>() or QStringList() (cf https://doc.qt.io/qt-5/qtquick-modelviewsdata-cppmodels.html). Change your Q_PROPERTY from QList<QString> to QStringList and it will work as expected.

@GrecKo , I mean without the button, when I edit the values of TextEdit, I should be able to get the modified text. I tried via property. It always gave me empty

@LeLev Thank you very much for your answer. It helped me to understand my issue a little more. So I tried your code, and it works, meaning that the ListView isn't eating the Space key. However my interface is a little more complex than this one, it contains other objects like SwipeView, and yes, my items contain components like buttons which may take the focus. However I already tried to deactivate them and even thus the issue remained. I played a while around the code you posted. I noticed that the following code no longer receives any key: Rectangle { anchors.fill: parent color: "transparent" visible: true SwipeView { anchors.fill: parent activeFocusOnTab: false Page { background: null ListView { id: view anchors.fill: parent spacing: 2 focus: true model: ListModel { ListElement { name: "el1" } ListElement { name: "el2" } ListElement { name: "el3" } } delegate: Button { focus: false focusPolicy: Qt.NoFocus onFocusChanged: {if (focus) focus = false;} width: parent.width height: 50 text: index === view.currentIndex ? "currentIndex" : modelData onClicked: { view.currentIndex = index } } Keys.onPressed: { console.warn("key clicked"); if (event.key === Qt.Key_Space) { console.log("space clicked"); console.log(view.model.get(view.currentIndex).name); // view.model.get(ind).name = "new value" event.accepted = true; } } } } } } So I assume that some components operate like filters and may stop internally the keyboard signals, or at least a part of them, without let the choice to the developer to bypass this behavior (or at least I don't know how to do). To be honest I'm a little puzzled, because I worked for15 years with the Windows API before changing for Qt, and receiving a keyboard notification was never an issue, even when the parent component already received it before (in fact it was the contrary: the message could be blocked in the parent, but by default it was passing). So now the question is: in the above code, how can I receive the keyboard signals, and in particular the Space key, in my ListView despite of the parent SwipeView? Or which solution is normally used in a such situation, e.g is there a way to globally listen the keyboard and intercept keys in the Windows level, BEFORE any component receives them?

Just an update, not sure if this is the reason for the behavior described above, but I had two ListView properties set to values, which could be contributing to this: preferredHighlightBegin: Math.floor(width/2) preferredHighlightEnd: Math.floor(width/2 + 1) I noticed that to trigger the issue I had to resize the window, so it makes sense to me that once I resized the window the preferredHighlight area would be not in the center, while positionViewAtIndex would position the item exactly at the center, which would then cause currentIndex to be updated to the next item.

@jeanmilost said in ListView - How to refresh rows which content changed without slowdown?: view.model.dataChanged(view.model.index(0, columnCount - 1), view.model.index(rowCount - 1, columnCount - 1)); So you are emiting dataChanged from QML? That seems like a bad practice, why can't you do that in the model?

@ThMars then check the itemsIndex property of the returned object

@fcarney I am new to Qt so don't anything about Loader and Can you please take a look at this question too: https://forum.qt.io/topic/111852/inconsistency-between-model-and-view-while-updating-qsqltablemodel-cell

@Christian-Ehrlicher It caches entries that could have fairly high resolution images in them. 100MB consumed is quite reasonable for my particular use case. I've solved my problem my creating a general-purpose list model class which does not retain too many recent items in memory, and then implementing an application-specific subclass that will automatically produce small, low-resolution thumbnails and save them to a separate table to allow for faster loading later on.

@fcarney Easy as that. This works perfectly fine with just a ListView. I added a ScrollBar to it and I have the same without any binding loops. Thanks!

@Shrinidhi-Upadhyaya thank you very much! it solved the issue

Ah, I found the problem. I was telling beginInserRows I was going to insert at the end and then not inserting at the end. Telling it the right place solved the problem.

@VRonin said in How to propagate changes in SingleTon type custom QAbstractListModel on QML ListView?: @qml.newbie said in How to propagate changes in SingleTon type custom QAbstractListModel on QML ListView?: m_hackNewsList.append(HackNews{id, deleted, type, by, time, text, dead, parentId, pollId, kidsIdList, url, score, title, partsIdList, descendantCount}); You need to call beginInsertRows/endInsertRows before/after m_hackNewsList.append(HackNews{id, deleted, type, by, time, text, dead, parentId, pollId, kidsIdList, url, score, title, partsIdList, descendantCount}); I have now added these lines but even now it's not working. Could be down to something I did wrong in the main.cpp where I'm registering the model for qml? The main cpp file is as below. #include <QGuiApplication> #include <QQmlApplicationEngine> #include "NetworkRequestMaker.h" #include "HackNewsModel.h" int main(int argc, char *argv[]) { QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling); QGuiApplication app(argc, argv); NetworkRequestMaker testRequestMaker; qmlRegisterType<HackNewsModel>("Hacknews", 1, 0, "HackNewsModel"); QQmlApplicationEngine engine; const QUrl url(QStringLiteral("qrc:/main.qml")); QObject::connect(&engine, &QQmlApplicationEngine::objectCreated, &app, [url](QObject *obj, const QUrl &objUrl) { if (!obj && url == objUrl) QCoreApplication::exit(-1); }, Qt::QueuedConnection); engine.load(url); return app.exec(); }

@JonB Thank you for your explanation. I understand what i need to do, but i need a little help in making the right signals and slots. My project was setup using the "Using C++ Models in QML {tutorial}" as a guide. here the ToDoList class is set as the data in ToDoListModel class. In the ToDoList Calss there are: 1.appendItem() function, which emits the signals preItemAppended() and postItemAppended() 2.removeItem() funciton, which emits the signals preItemRemoved() and postItemRemoved() [these work fine] 3.similar to the appendItem() and removeItem() I am trying to make a setItemAt() function that will modify the existing data. but there was no steps in the tutorial to indicate how i could notify the model to emit the dataChanged() signal. I tried making my own signal in the data class and a slot in model class but i couldn't figure out how to connect them. the main function has a ToDoList object but no ToDoListModel object (ToDoListModel is just registered to qml). i am only familiar with using the connect(*sender,signal,*receiver, slot) function to connect. I suspect that it has something to do with the 'Q_PROPERTY(ToDoList *list READ list WRITE setList NOTIFY listChanged)' line in the ToDoListModel header file. following the tutorial I removed the NOTIFY listChanged part. summary:which signal do i need to emit from the data class(ToDoList) to have the model class (ToDoListModel) emit the dataChanged() signal?

Hi @J-Hilk vielen vielen Dank. Das hat mir sehr weitergeholfen und es funktioniert jetzt dank Deiner Hilfe. Eine schöne neue Woche wünsche ich Dir. Grüße Sven

Had the same problem. Fixed it by not binding the object referenced by the role to a property and using the property but using the role name directly to acces the model item. Instead of property MyItem myItem: model.object text: myItem.foo try text: model.object.foo

Can we finally see where and how you emit dataChanged()? And with which indexes?

Waiting for guide "How to avoid JavaScript models in Qt and why should you care" (performance, memory usage)

Indeed it works ! I did 2 mistakes, I forgot ".item" after currentItem and I didn't changed currentIndex when I switch between pages because I use positionViewAtIndex. But positionViewAtIndex don't change currentIndex of the listView. Thanks guys !

@gabor53 If you can provide a complete example then I can see the issue first hand then as it seems like it should work, but it is hard to say without seeing it.

@GrecKo oh thank you very much. I confused bottomMargin for anchors.bottomMargin. I wasn't aware of this property being available. This is exactly what I needed!

Hi , you can use the SwipeView property interactive, to look when ListView are scrolling and enable in ListView when SwipeView scrolling

In this case, the color of the model item is being changed somewhere in the backend You don't require to do this. This is where Model View framework comes into picture. color change should automatically taken care by the model itself. I'm assuming that you have written custom model. Are you sending the dataChanged(..) signal whenever data is changed at model ?

Thanks for the feedback. I have a follow up question though. Where are QML's default role names documented? I couldn't see the list. It would save me a lot of time. EDIT Here they are: link.

Found those three properties completely randomly on a completely unrelated topic post... Dropping them right here, just in case someone needs it : clip: true boundsBehavior: Flickable.DragAndOvershootBounds snapMode: ListView.SnapToItem They're doing about everything i need. I think that's a common problem beginners fall into but there is not that much topics about it.

I am not finding the way to do this: to have ListView virtualization in all ListView usages. Someone is able to undertand why?

@jpnurmi said in ListView and PageIndicator - PageIndicator is not updated: The bindings are fine. The problem is that the ListView has only snapMode set, but highlightRangeMode seems to be missing. Therefore the ListView is not changing its currentIndex while flicking. snapMode does not affect the currentIndex. To update the currentIndex as the list is moved, set highlightRangeMode to ListView.StrictlyEnforceRange. https://doc-snapshots.qt.io/qt5-5.9/qml-qtquick-listview.html#snapMode-prop Thank you @jpnurmi. The following line solved the problem: highlightRangeMode: ListView.StrictlyEnforceRange Somehow I missed another thread: https://forum.qt.io/topic/81429/listview-does-not-change-currentindex-when-scrolling/6