Did you saw the third argument of the signal ? The one you are currently not using in the code you provided. It's the one containing the custom roles.

You can get StackView instance from Profile.qml quite easy, using StackView attached properties. Define new property at your StackView: StackView { id: home property var modeldata: null // Define StackView property initialItem: Pane { ... ListView { ... delegate: SwipeDelegate { ... swipe.onCompleted: { if (swipe.position > 0) { home.modeldata = model; // Set StackView property home.pop(); home.push("Profile.qml"); } ... } ... } } } } And then at Profile.qml you can easily get attached StackView property: Pane { id: profile ... Button { ... text: "Delete" onClicked: { let modeldata = profile.StackView.view.modeldata; // Accessing StackView property via attached properties if (modeldata !== null) { user_model.removeRow(modledata.index); } ... } } } In this case you do not need workaround with helper row. Also if you need some objects like your helper - better way is to use QtObject rather than visual 'invisible' object.

@Ahti Perhaps not relevant, but can't help noticing: your removeRows and its call to beginRemoveRows() correctly allows for multiple rows, but your call to response = model->removeRow(first, QModelIndex()); only allows for one row. That's works for your del_row(), but not in general. I don't suppose fixing that changes behaviour?

@Ahti said in Inconsistency between model and view after removing a row from a table: JsonObject u_data; u_data.insert("id", model->record(index.row()).value(0).toInt()); u_data.insert("name", model->record(index.row()).value(1).toString()); if (role == Qt::DisplayRole) return u_data; That's inefficient. If you only support DisplayRole, then you can move that QJsonObject directly into that if statement. if (role == Qt::DisplayRole) { QJsonObject u_data; u_data.insert("id", model->record(index.row()).value(0).toInt()); u_data.insert("name", model->record(index.row()).value(1).toString()); return u_data; } Second, you should use the parent here, even if it is a flat list: beginRemoveRows(QModelIndex(), first, last); response = model->removeRow(first, QModelIndex()); beginRemoveRows(parent, first, last); response = model->removeRow(first, parent); But why you get this strange behavior when removing - I don't know. Perhaps it has something to do with the fact that you have two models here - UseModel is a list model and your model variable is a QSqlTableModel (which inherits from the same base class as list model). Perhaps these calls get duplicated, although it is unlikely. Try adding some qDebug() calls into removeRows(), or run it through a debugger, to see what is happening.

Hi @Joel-Bodenmann , thank you, I got the point about the item delegate but I see two issues: implement a drag and drop listview because I ended up with empty lines (on the list view) and fields on the widget mapper: https://s32.postimg.org/47yyrq7id/Untitled.png implement a delegate that paint a checkbox with custom pixmap, the input with number and the input with text.

@tokafr said: Mydelegate *delegate = new Mydelegate; hi, i might miss something but why dont you just create another instance? Mydelegate *delegate2= new Mydelegate; view2 -> setItemDelegate(delegate2); Normally a delegate (instance) is not shared between views as its not intended.

Hi, It depends on your implementation. Generally speaking, you trigger the whatever is needed to grab the data over the network and once you have it you populate your model and if done correctly, this will trigger the machinery that will make all view aware that new data are available and they should update. Hope it helps

@Valerian I did not do d&d yet. In my idea you should register a signal to be emitted whenever you move mouse in the area of new position and call swap function. Do you feel something like this?

Hi, IIRC it should already be done. What do you have in your delegate ?

Do you have an example of this?