You can use ItemDelegates: TableView { id: tableView anchors.fill: parent model: TableModel { TableModelColumn { display: "column 0" } TableModelColumn { display: "column 1" } rows: [ { "column 0": "value 0", "column 1": "value 1" }, { "column 0": "value 0", "column 1": "value 1" } ] } delegate: DelegateChooser { DelegateChoice { column: 0; ItemDelegate { contentItem: Label { text: "delegate column 0: " + model.index } } } DelegateChoice { column: 1; ItemDelegate { contentItem: Label { text: "delegate column 1: " + model.index } } } } }

@Volodymyr-Mudryk Boot2Qt is commercial software, so you can ask QtCompany directly for support

I see this is an old thread and I see several unresolved threads on this topic. I'm leaving this incase it helps someone else who ends up here. The solution was twofold for me. Go to File > Export Project and select Enable Python Generator. This will create a main.py. Make sure you pip install PySide6-DS Hope this helps someone.

Hello i am using WinCC OA to develop a qt application. WinCC OA has some custom elements which cannot be detected by squish for example a polygon. Squish is now not able to detect this element with the picker. I know the name of the element but as it is of WinCC OA internal i do not know the type: waitForObject( {"container": "container", "name": "POLYGON1","type": "???","visible": 1} ); How do i get this information? And what to use if unknown? Is there any other way? I mainly just need to click this element. Thanks a lot

By the way, my test is now deleted from the platform...

@swankster Just so I understand. You have 56k rows of 12 columns. You want to be able to sort ASC or DESC by 4 columns. So what you do is populate 8 datasets/models each with 56k records with each of the resulting sorted orders. And you convert the received tables to CSV for serialization and deserialize for display. On top of which you copy that to a QContiguousCache. This sounds like a lot of work and a lot of memory. Not to mention it only works while the data does not change or need to be re-queried. I always ask people if they really need that many rows displayed to the user at a time, because the user cannot visualize 56k rows? Even if you do I believe we have had people display like a million rows without saying it's too slow. And nobody has mentioned QContiguousCache before. If you are prepared to do your sorting at the SQL side the usual way for large datasets is to use QSqlQueryModel::fetchMore() to receive data rows in "chunks" as and when needed. I believe it only starts by fetching 256 rows and you have to call this to fetch further groups of 256 rows. You usually do this in response to the user scrolling the table view as required; you may also do some asynchronously on a timer. Have you actually tried something like this? As I say I am a little "surprised" that you say you need all your stuff to make it acceptable. P.S. Just checking: in your QTableView you do not use setIndexWidget() for any of the items/columns, do you?

@Pl45m4 Ja ist eingebunden. Allerdings bekomme ich dort von clang-tidy ein file not found. Das ganze läst sich aber fehlerfrei compilieren.

@RokeJulianLockhart to the best of my knowledge, no. The first release of Discourse was in 2014 and the forum is several years older than that.