model/view

[user4592357]

@raven-worx
the cells are a lot actually

and about your code snippet, what if the row/column values aren't known beforehand?

[VRonin]

@raven-worx said in model/view:

If we are not talking about hundreds to thousands you can also use QStandartItems

I actually use tens of thousands tree elements with QStandartItemModel and works for me

[raven-worx]

@VRonin said in model/view:

I actually use tens of thousands tree elements with QStandartItemModel and works for me

i never said it's not working, but it's a waste of memory.
And thus discouraged to do so (from my side).

[user4592357]

@raven-worx
about your code snippet, what if the row/column values aren't known beforehand?

[raven-worx]

@user4592357
then reusing the QHash structure is not ideal, you could use your matrix approach then

[user4592357]

@raven-worx
can't i use QTableWidget and QTreeWidget since my models aren't reused?

[VRonin]

@user4592357 That's basically the same as using QStandartItemModel that we suggested at the beginning

[user4592357]

@VRonin
how is it the same?

should i use the same QStandartItemModel for both views?

[VRonin]

I mean QStandartItemModel + QTreeView = QTreeWidget and QStandartItemModel + QTableView = QTableWidget

[user4592357]

@VRonin @raven-worx
i have another question.

so my table widget consists of 2 widgets: QTableView and a QTextEdit under it to display info about a particular cell.

the data container i use to set model data consists of two maps:

1. data storage for table view
2. data storage for text edit

how should i handle this in data()?

[user4592357]

should i user two different containers???