How to simplify syntax

[JacobNovitsky]

Lets say, I selected line 1 3 and 9
or I selected lines 1 2 3
I need to 1) select only 123 out of 9 lines total
2) I need to get selected indices :)

[VRonin]

In your code you have tableView->setSelectionBehavior(QAbstractItemView::SelectColumns); that makes it so when you select a cell, the entire column gets selected. I don't believe that's what you want, delete that line

[JacobNovitsky]

https://justpaste.it/dwq1c
Above is my last working code, it selects rows line by line as requested,
but outputs
Selected columns: QList()
with no inidices

I believe problem in
QList<int> MyWindow::getSelectedColumns()
Need to clarify/fix this syntax

[VRonin]

Yes, you need to revert to selectedIndexes instead of selectedColumns. My suggestion above was a misunderstanding of your requirement

[JonB]

@JacobNovitsky
I'm not sure I follow. If the user selects "lines" (rows) then you won't get any selected columns back? (Because whole columns are not selected, just certain columns within certain rows.) To see which columns are selected within various selected rows use QModelIndexList QItemSelectionModel::selectedIndexes() const, which gives all selected cells and then look at the column() values within that. If that is what you are looking for.

[JacobNovitsky]

@JonB oh, it does indeed outputs columns selected, but I really meant rows :)
So I do look for the same but for rows?

[JonB]

@JacobNovitsky
Well, yes!
There are 3 methods to see what is selected:

• selectedColumns() --- just complete columns selected.
• selectedRows() --- just complete rows selected
• selectedIndexes() --- any mix of individual cells (not necessarily contiguous) selected. Always valid. Inspect each item's row() and column() to see what they are, could have any values.

[Pl45m4]

@VRonin said in How to simplify syntax:

That walks like a table, quacks like a table and swims like a table

LMAO :D

[VRonin]

@Pl45m4 It's science: https://en.wikipedia.org/wiki/Duck_test

[Pl45m4]

@VRonin

Haha nice one. I know Rubberduck Debugging but this was new to me :)