Finally I solved it!!!

function fillRow() { table.model = undefined // <--- 1 if (!tableModel.count) { tableModel.append({"C0":50}) } else { tableModel.setProperty(0,"C"+(table.columnCount-1),50+table.columnCount-1) } table.model = tableModel //<--- 2 var x = tableModel.get(0) console.log("Num. Columns",table.columnCount,"row object",JSON.stringify(x)) }

When I fill the columns, I set TableView.model to undefined(1), then fill the rows, and after I set TableView.model to ListModel again(2)

I like it when you do QtQuick !

Hi, I finally got the latest 5.6.0 baseline compiled for iOS and can confirm that 5.6.0 does not show this tableview error.

Thanks for your help, well appreciated !!

BR,
Thomas

Your two images show two different tables. Are you sure that both tables contains data ?

Thank you. It worked!

You would at least need two radio buttons for that. But it sounds a bit unusual for a UI especially for a database.

Sounds like you want to use both a custom widget using QDataWidgetMapper and a QTableView at the same time.

SOLUTION:

ui->tableView->model()->setHeaderData(2,Qt::Horizontal,QFont("Arial",10,QFont::Bold),Qt::FontRole);

Actually everything is stated in the Qt Help, - just need to know how to correctly use it :)

Thank you. It worked.

Thank you. It worked.

Thank you.

Thank you all. It finally worked.

Ive been looking into this a bit more myself and ive found that the TableView headerVisible property makes a big difference. I am currently hiding the header.

When headerVisible=false then tableView.__listView.columnAt(x) always returns -1.

When headerVisible=true then tableView.__listView.columnAt(x) works correctly.

Id like to keep the table's header hidden if possible, hopefully a workaround for tableView.__listView.columnAt(x) is possible.

Also, im on Windows with Qt5.5.1 mingw if that makes any difference.

@Chris-Kawa thanks, i now see the thing.
I've found example http://doc.qt.io/qt-5/modelview.html#2-5-the-minimal-editing-example but it use QAbstractTableModel and i'm using a QSqlRelationalTableModel instead of QSqlTableModel.

Will it still works for relations ? I can't found an Abstract for RelationalTableModel.

@SGaist That's pretty close to what I like to achieve. Unfortunately I am using a QML TableView. The only difference to the FrozenColumnExample is that my Frozen Rows have a dynamic count. A binary role in my table model determines to which section the entry belongs to. I will try to adapt the FrozenColumnExample to my case in QML. That was my idea anyway, but I was hoping for more simple solution ;) Substituting the sections with seperate TableViews and using a QSortFilterProxyModel to simulate the section behavior is the way to go I guess. Thx for your tip.

@KiNgFrUiT You're Welcome :) Thanks for sharing the complete solution. Also it would be better if you mark the post as solved so that others may know that the post has a solution.

I think I found the answer. I missed this very important sentence:

"Some of the described features are only available in the commercial version of Qt Creator."

I bet that's it.

@p3c0 This sounds like a very easy solution, I'll try it out. Thank you.