Changing column order in a QTableView?

[giesbert]

You can even reimplement them with QSFPM, so using this could be easier

[ZapB]

True and if other functionality of QSFPM is also required that would indeed be the way to go.

[andre]

I would use a much simpler approach, without any subclassing.
QTableView provides access to the header view via QTableView::horizontalHeader(). QHeaderView has a method called moveSection, that allows you to reorder the sections (in this case: columns) as you please.

[ZapB]

Of course. I forgot about that method. ;-)

[dangelog]

[quote author="Andre" date="1300615403"]I would use a much simpler approach, without any subclassing.
QTableView provides access to the header view via QTableView::horizontalHeader(). QHeaderView has a method called moveSection, that allows you to reorder the sections (in this case: columns) as you please.

[/quote]

That's exactly what he's doing, so there's something else going on (wrong section numbers?)

[andre]

[quote author="peppe" date="1300626770"]
[quote author="Andre" date="1300615403"]I would use a much simpler approach, without any subclassing.
QTableView provides access to the header view via QTableView::horizontalHeader(). QHeaderView has a method called moveSection, that allows you to reorder the sections (in this case: columns) as you please.

[/quote]

That's exactly what he's doing, so there's something else going on (wrong section numbers?)[/quote]

Not exactly, but close, you're right. scarleton, could you insert some debug statement to see the actual values of the sections you're trying to swap?

André

[scarleton]

Well, I added extracted the values:

@productTableHeaderView->setMovable(true);
int priceVisualIdx = productTableHeaderView->sectionPosition(_priceListItemModel->priceNo());
int imageMaxVisualIdx = productTableHeaderView->sectionPosition(_priceListItemModel->imageMaxCntNo());
qDebug("priceVisualIdx: %d imageMaxVisualIdx: %d", priceVisualIdx, imageMaxVisualIdx);
productTableHeaderView->swapSections (imageMaxVisualIdx, priceVisualIdx);@

priceVisualIdx: 100 imageMaxVisualIdx: 300

[dangelog]

So, it's likely that those values are actually the position in pixels of those sections. If
@
_priceListItemModel->priceNo()
_priceListItemModel->imageMaxCntNo()
@
are correct (i.e. they return the logical column index), you can pass them directly to swapSections.

[scarleton]

That was it, thank you!

[andre]

I can imagine the swap did not work between column 100 and 300, in any way :-)