Suitable "editable list" widget?



  • Qt5. I'm sure it's been asked before, but how much work is it/is there an existing example for a (fairly) simple "editable list" widget?

    By that I mean: the ability for the end user to add, delete and update elements in a list. My first thought was a QTableItemWidget/QTableView. However, while the in-place editing is fine, there is no support for add or delete row.

    My requirements are very straightforward:

    • I only have a single column in the proposed data/list, it's a string. So I don't care about multiple columns or headers etc.
    • It's any old string, so no dropdown for options.
    • But I do need some sort of "delete this row" button/link (and possibly "edit this row" too for clarity, rather than relying on user to click into cell directly, but that's optional)
    • And some sort of "add another new row at the bottom" button/link.

    Really fairly standard stuff used in many apps.

    That will do for one of my two places I need this. The second one has a little wrinkle: I need a Select ... button on each row (in a column at the right or similar) which the user can press, goes into a dialog, picks something, and we copy that back into the data column cell. So still only a single column of data, but ability to add a button.

    Now, I write in Python. I don't want to have to pull in any third-party (e.g. KDE?) widgets, please. And I believe in minimal code to achieve a minimal user experience ( :-; ), so I'm hoping for a few lines of code/example/suggestion rather than an "essay" for this.... :)

    EDIT Here's one from a web app of mine. Don't get hung up on the details. Just the idea:

    0_1542895592838_tmp.gif


  • Lifetime Qt Champion

    Hi,

    The usual thing to do (and you can find that for example in macOS's interface) is to have a + and - buttons at the bottom or the top of your QTableWidget/View to add/remove element. The - button being only enabled when something is selected.

    Do you mean you want the "Select" text on your button or have a hint with ... on the second column ?


  • Moderators

    @JonB
    use QListWidget for example
    for adding: listWidget->insertItem(listWidget->count(), item);
    for removing: listWIdget->removeItemWidget(listWidget->currentItem())

    or QListView with a custom model, but this is more work to implement the model correctly



  • @raven-worx
    I know how to do insert/removeItem() programmatically, that's not the question. The question is the user interface --- presenting a "delete/edit" against each item/row, and a "add new row" at the bottom of the whole list or in a dummy item at the end or whatever.

    I'm pasting an example into my original post....



  • @SGaist
    Thanks, that's closer. Rushing out now, will answer later on....



  • @SGaist

    • OK, the way you approach it is to have just one table-wide button to do something, and rely on a current item being selected by the user. My way (inherited from ASP.NET) is not to have a selection and instead have necessary buttons on each row. I didn't think of yours. If that's more usual, and it sounds simpler, I'll do it that way. Also if I won't need columns for buttons, I could just have a simple QListWidget instead of a QTableView since I only have one data item cell, sounds good!

    • For the "selection" case. Instead of just typing into the data cell, the user needs something to click to take him to a dialog. I don't much care what that is. I was thinking of a ... button say to the right of each cell. But that will introduce a new column/widget, it won't be so easy to just do as QListWidget, and I don't know if QTableView allows columns just for widgets instead of the data. However, your new way I could just add one ... button, like one add and one delete, at table-level to use on whatever row is selected, which would solve.

    My one reservation is user having to understand that buttons for doing stuff on whatever is selected are at top/bottom. It saves on space, but it doesn't seem so immediately intuitive to me as having the buttons on each row. I don't use mobiles/Apples :) Is that a good way to do it? Anyone have a screenshot of what it looks like on some device? :)



  • For an intuitive insertion-at-bottom interface you can have a look at this library using Insert Proxy Model (I'm trying to also get this proxy included in Qt 5.13). You can find example usage here

    for the remove/edit buttons you can use KExtraColumnsProxyModel from the KDE library (that module works on all platforms). You just need to return a pixmap as Qt::DecorationRole for the extraColumnData() and connect the clicked signal of the view to a slot that deletes the row or changes the flags() of the model to make it editable.

    Basically:
    source model -> KExtraColumnsProxyModel -> InsertProxyModel -> view

    or
    source model -> KExtraColumnsProxyModel -> view
    if you want the insert button as you have the edit and delete ones



  • @VRonin
    Thank you for your detailed answer. In my case I did say I don't want to have to bring in new libraries, like the KDE one. Remember I'm also Python/PyQt, makes life much harder. I realise that's my choice.

    I think I can roll my own adequately if I follow @SGaist's interface, and use row selection with a table-level button acting on it. Avoid columns and do the whole thing as a QListWidget hopefully.

    Yours is probably closest to what I am used to. (And I have noticed that KDE seems to be what offers the "extra stuff you can do with columns" etc. I am used to compared to Qt's in-builts.) But it breaks my "minimal code" desire, no offence intended!


  • Qt Champions 2017

    @JonB said in Suitable "editable list" widget?:

    My one reservation is user having to understand that buttons for doing stuff on whatever is selected are at top/bottom. It saves on space, but it doesn't seem so immediately intuitive

    Well, quite often when working with tables you have context menus for that purpose. Take excel or open office spreadsheets as an example. There are 3 elements that are "duplicates" to make the UI as intuitive as possible for inserting rows above/below selection and deleting the selected row (just an example, but it applies to other operations as well):

    1. The menu - you get an entry that's enabled/disabled.
    2. The toolbar - same thing, but you have a button and and an icon (usually it's customizable as well).
    3. Context menu - right clicking gives you options pertaining to this particular UI element (like the main menu, but shorter).

    As a side kick, which I intentionally didn't include in the above list:

    • Keyboard shortcut(s) - yet another way to trigger one of the above

    So my best advice is to implement all of those (if possible).



  • @kshegunov
    So: menu, toolbar, context menu & keyboard shortcut. That will all fit it into the 5 lines of code I expect to have to write to get this going, right?


  • Qt Champions 2017

    @JonB said in Suitable "editable list" widget?:

    That will all fit it into the 5 lines of code I expect to have to write to get this going, right?

    Right. But when was the real solution as simple as we thought initially? Does such a unicorn exist?

    Seriously though, it boils down to creating one QAction and just adding it wherever it's supposed to go - menu, context menu, toolbar w/e.



  • @kshegunov
    I was about to plonk down one QListWidget/QTableWidget plus a couple of QPushButtons below it to do add/delete row in their clicked() signal's slot (right?). Why do I want/what benefit will I gain if I introduce a QAction? Sorry if this is dumb, I may have forgotten....


  • Moderators

    @JonB said in Suitable "editable list" widget?:

    Why do I want/what benefit will I gain if I introduce a QAction?

    to reuse the functionality in a menubar/toolbar/contextmenu for example



  • @raven-worx
    Yep, got it, thought so. So it's up to me: if I never want those (for right or for wrong) and only do clicked, I don't need a QAction.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.