@GrecKo Dear GrecKo,
in the qml_singleton.h should I change the word "Type" to "System", because my Particlesystem is called like that?
Where have I to introduce my Hardcore_Entrymodel - is it the UnsafeArea or is it the ApplicationUI class?
I tend to UnsafeArea=Hardcore_Entrymodel and to leave the names "ApplicationUI" and "Type##QmlSingleton", but I'm not sure ...

@jdent
I am not exactly sure, what

update the new record

means. Update an existing record, or insert a new one?
insertRecord()adds a new record to your table model. It doesn't do anything with the record's data.

but with what row number

That depends.
currentIndex()is the currently selected index of any QAbstractItemView. It has a column()and a row().
indexAt()will return the model index at a given point on the screen.
indexWidget()returns the pointer to a widget, in case you have set one.
In the model itself, you have plenty of accessors to retrieve or set item data to a given model index. All of those examples can be used to modify existing records (actually: indexes).

You can add custom functions to e.g. bulk-add data to the model but must not forget the call the appropriate changed signals. This is a common way of adding data since it's to slow through setData() when a lot of stuff is changing.

@JonB

Huge thanks, you solved the puzzle for me!

If you use the the same model instance in more than one place they will always have the same index. This may, or may not be what you want. FYI

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.

@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?

I'm sorry but I don't think will compile.
Please provide a minimal, compilable example which shows your problem. E.g

int main (int argc, char **argv) { QApplication app(argc, argv); QTreeWidget treeWidget; QTreeWidgetItem *cities = new QTreeWidgetItem(&treeWidget); cities->setText(0, "Cities"); treeWidget.show(); return app.exec(); }

See http://doc.qt.io/qt-5/qtreewidgetitem.html#details

Finaly I have finished my little example!

Previous version have been really buggy in items move. So I have to subclass from QAbstractItemModel. Many thanks to @Patou355 with his solution.

NB I haven't deal with mousePressEvent() yet.

You can use either QTreeWidget, QTableWidget, QTreeView+QStandardItemModel, QTableView+QStandardItemModel, QTreeView+QAbstactTableModel subclass, QTableView+QAbstactTableModel subclass for what you are trying to do.

I would go with a QT*View+QStandardItemModel (tree or table doesn't matter).

The functionalities you describe are:

only some columns will be editable

use QStandardItem::setFlag

Entering a value in the cents column (a logarithmic measure of frequency) will change the value in the hertz column, and vice versa

connect a slot to QStandardItemModel::dataChanged signal

There will be a button next to the table to add an additional note to the scale

connect a slot that calls QStandardItemModel::insertRows to the QPushButton::clicked signal

Hi
Mr @VRonin suggested we looked at
http://doc.qt.io/qt-5/qabstractscrollarea.html#maximumViewportSize
so maybe yo u need to subclass view and return full area.

Interestingly, if I make the plugin static, it works fine. Only when the plugin is dynamic does this error happen... Very strange.

The issue was solved by registering the C++ model with QML as an Instantiable Object Type as described here and then instantiating the model from QML for each new search page, as described in this topic: Is it possible to expose a C++ Class that doesn't have a default constructor to QML ?
Thank you for everyone who tried to help!

@SergeyK12 said in Unite data from two QSqlRelationTableModel into one TableView:

I reimplement the following method of QIdentityProxyModel:

data, index, columnCount
add a private field with QSqlRelationTableModeland the setter.

I suppose there is something alse which i should reimplement to make field in 5 cell editebel. SetData ofcource, but why is it in a gray mode? There is a method which make cells editable?

You can't have a proxy model with 2 source models. internally it will rely on mapFromSource and mapToSource which won't work in your case, start directly from QAbstractItemModel.

The methods you reimplemented are fine, you miss rowCount(), setData() and flags()

use KDE (but its too hard to build a library).

no it's not... detailed instructions to build any tier 1 KDE module (spoiler alert: it's only 9 cmd lines): https://forum.qt.io/topic/76533/copy-selected-rows-of-a-table-to-a-model/12

@michalos I'm not sure if I can help you but seems like model test code works for me.

What I did:

Added modeltest.h and cpp into my project Added "testlib" into "QT" section of project file Added this to modeltest.h: #include <QtTest/qtestcase.h> #define qVariantCanConvert(_type_, _var_) _var_.canConvert(QMetaType::_type_) Changed expressions like "qVariantCanConvert<QString> ( variant)" to "qVariantCanConvert(QString, variant)" in modeltest.h

And... my sample model failed to pass the test of course :D

Technically you have a two-level tree.

You can still use that example as a base. In place of their custom TreeViewItem you have your Parent and Child.

Those the abstract model would be a wrapper around your Parent/Child combo.

@VRonin Seems like good solution. I'll definitely will try this. Thanks.

@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.

I think I take your meaning. As I geared up to subclass QAbstractItemView, it also became evident how niche my new class would be. Based on this, I decided to take your advice of composing a custom widget.

If anyone should want to subclass QAbstractItemView, this is a good article to get you started.