What's the best way to add a remove button to each row in a QTableView (without modifying the model)
Is there anyway to do this in a delegate (the model doesn't have a row for the button)
Printable View
What's the best way to add a remove button to each row in a QTableView (without modifying the model)
Is there anyway to do this in a delegate (the model doesn't have a row for the button)
In the delegate you should draw something that looks like a button using QStyle and handle events for clicking such artificial button.
Thx for the answer, this was not what I was hoping for :p
I was thinking of using a proxymodel to add the extra column and add a styleddelegate to it, dunno if this is possible
just was checing into QProxyModel but it says its obsolete, it looks like i will need to write my own. oh just found that there is a QAbstractProxymodel I can use
I've just tried it and it seems to work with a QAbstractProxymodel and a delegate.
The proxymodel just adds an empty column and the delegate creates an pesistent editor in it (a modified QPushbutton)
It's not clean but it works
Smart thinking.....Quote:
Originally Posted by StrikeByte
Can you use the QSortFilterProxyModel? It is not marked as deprecated / obsolete.
http://qt-project.org/doc/qt-5/qsort...roxymodel.html
I started to suggest this yesterday, but didn't have the time to complete my reply. Glad you tried it and got it to work.Quote:
I've just tried it and it seems to work with a QAbstractProxymodel and a delegate.
The proxymodel just adds an empty column and the delegate creates an pesistent editor in it (a modified QPushbutton)
QSortFilterProxyModel is not appropriate for this use. It is used in cases where you want to 1) remove certain rows or columns from the source model and / or 2) display the source model sorted in a different order without changing the source model. There are several additional methods that must be implemented in QSortFilterProxyModel which have no relevance to the OP's problem. In his case, he wants to pass the source model unchanged, and simply add a new virtual column with a pushbutton in it. Depending on where he adds the virtual column, he won't have to do anything in QAbstractProxyModel's virtual methods except return QModelIndex instances that map directly to or from the same row and column of the source.Quote:
Can you use the QSortFilterProxyModel? It is not marked as deprecated / obsolete.
Did you try it with a large model, say... 1000 rows? What was the performance?Quote:
Originally Posted by StrikeByte
No sorry my model only contains like 50 rows
[edit]
just did a quick test with 5000 items, took 8 seconds (my model does some name checking an makes a unique name for each item, need to check it for a faster algorithm)
adding items to the model doesnt make a difference when using the proxymodel or not
scrolling through the list works just fine
I still do not know what happens on a slow pc
thx for the question, now I see I need to optimize my model a bit :p
[/edit]
Thx for the tip, but all the items are stored in a QMap already, with theire internal unique key.
The algorithm is making a unique name for the users input:
for example if a user adds an item called "test" if he/she tries to add another item called "test" it will rename it to "test_1", another "test_2",,, etc
If you are doing this in response to user input, then it is unlikely that performance will ever be an issue. Even if you have a large number of names stored, the time it takes to look one up in a QMap (whether it finds it or not) is negligible compared to human response time.