Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve 'Requested Payments History' Multiselect #684

Conversation

john-moffett
Copy link
Contributor

@john-moffett john-moffett commented Dec 5, 2022

The "Requested payments history" list has somewhat broken functionality. You can only select contiguous rows. Sorting the list unexpectedly modifies any selection you made:

Initially sorted by date and multiple items selected:

image

Now sort by label ->

image

The context menu appears when multiple rows are selected despite the actions only affecting the first in the list:

image

These issues are all corrected.

First, a QSortFilterProxyModel is inserted to take care of sorting instead of sorting the model manually. (This is the same approach taken for all other sortable lists in the GUI.) This also preserves any selections the user had made prior to sorting. Second, the selection model is changed to ExtendedSelection to allow for non-contiguous multi-select. Third, the context menu is disabled when multiple rows are selected, as none of the context menu options operate on multiple selected items. Update: now the context menu operates on multiple rows. It will copy the data to the clipboard separated by newlines.

image

@DrahtBot
Copy link
Contributor

DrahtBot commented Dec 5, 2022

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
Concept ACK hebasto, pablomartin4btc

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

Conflicts

No conflicts as of last run.

@hebasto
Copy link
Member

hebasto commented Dec 6, 2022

First, a QSortFilterProxyModel is inserted to take care of sorting instead of sorting the model manually.

Concept ACK on it.

Second, the selection model is changed to ExtendedSelection to allow for non-contiguous multi-select.

Why? There are no use cases for multi-select, aren't there?

Third, the context menu is disabled when multiple rows are selected, as none of the context menu options operate on multiple selected items.

Not sure if such a behavior is a user-friendly one.

@john-moffett
Copy link
Contributor Author

Why? There are no use cases for multi-select, aren't there?

The "Show" and "Remove" buttons act on multiple selections. If you want to select multiple entries to delete, for instance, non-contiguous multi-select could be useful. Right now you can only delete single or contiguous items.

Not sure if such a behavior is a user-friendly one.

I was unsure whether to disable the context menu completely or show it but have everything disabled. I chose the former option, but the latter is easily possible. I think the current behavior (only acting on the first in the selection) is arguably the worst.

It's also possible to change it to work with multiple items. For instance, "Copy address" could change to "Copy addresses" upon multiple selection and copy a comma-separated list of addresses that you've selected to the clipboard.

Happy for feedback on this point!

@john-moffett john-moffett force-pushed the 2022_12_FixReceiveCoinsMultiselect branch from 5ae5293 to 0705836 Compare December 15, 2022 16:44
@john-moffett
Copy link
Contributor Author

Updated to now show the context menu with multiple selections. The data is copied to the clipboard separated by newlines.

Example:

image

Results in the following copied to the clipboard:

bitcoin:TB1QETGUVSJCM80365PQ2GFT8NASVYYPMCG8FEWN3W?message=Message%20with%20no%20label%20or%20amount
bitcoin:mt2nX2QuRkWkRd2ewbE1mTZ1zaKUeBDEZs?amount=10.00000000&label=Legacy%20Address&message=For%20More%20Testing
bitcoin:2N1Qu4pSpTbCud8ToT9NJWW2PiDm7V97TSq?label=P2SH%20Segwit%20Address&message=For%20testing

The individual context actions are enabled only if all selected items have data for that category. For example, if only two of the three selected items have a "label", then the "Copy labels" context menu action is disabled. The "Copy URIs" and "Copy addresses" actions will always be active.

The recent payment requests list has somewhat broken functionality. You can only
select contiguous rows. Sorting the list loses the selection data. The context
menu appears when multiple rows are selected despite the actions only affecting
the first in the list. These issues are all corrected.

First, a QSortFilterProxyModel is inserted to take care of sorting instead of sorting
the model manually. This also preserves selection data when sorting. Second, the
selection model is changed to ExtendedSelection to allow for non-contiguous multi-
select. Third, the context menu now operates on multiple selections properly. It will
copy newline-separated rows of data if appropriate.
@luke-jr
Copy link
Member

luke-jr commented Jun 29, 2023

Would prefer the refactoring split into a different commit

@luke-jr
Copy link
Member

luke-jr commented Sep 15, 2023

Copy link
Contributor

@pablomartin4btc pablomartin4btc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concept ACK and tACK

image

I agree with the improvement/ fix of non-contiguous multi-select behavior, it's something that a user have in most apps.

The grayed-out of the context menu items behavior is something that's already in master and it's not part of this PR, just to avoid any confusions.

The individual context actions are enabled only if all selected items have data for that category. For example, if only two of the three selected items have a "label", then the "Copy labels" context menu action is disabled.

For this specific case, I'd add another improvement/ fix which would be a tool-tip indicating why the action is disabled:
image

Same for the following statement, it's currently in master, since those fields are not optional when a user creates a payment/ new address.

The "Copy URIs" and "Copy addresses" actions will always be active.

I agree with @luke-jr in the split of the code into x commits, I took a quick look at his proposal. I like more the fact that the text of the action changes to its plural form when multi-select is performed as the author of the PR propose here.

I'd also add another feature, if possible, or maybe on a follow-up. that would be to add another context menu action to "Select All", and maybe just "Copy" with a tool-tip indicating that "All fields of the selected row will be copied". But as @hebasto mentioned above, perhaps there's no real use case for what I'm proposing here.

@DrahtBot
Copy link
Contributor

DrahtBot commented Feb 5, 2024

🤔 There hasn't been much activity lately and the CI seems to be failing.

If no one reviewed the current pull request by commit hash, a rebase can be considered. While the CI failure may be a false positive, the CI hasn't been running for some time, so there may be a real issue hiding as well. A rebase triggers the latest CI and makes sure that no silent merge conflicts have snuck in.

@hebasto
Copy link
Member

hebasto commented Feb 11, 2024

@john-moffett Are you still working on this PR?

@pablomartin4btc
Copy link
Contributor

I could take this to move it forward @john-moffett, if you are not able to, please let me know.

@DrahtBot
Copy link
Contributor

🤔 There hasn't been much activity lately and the CI seems to be failing.

If no one reviewed the current pull request by commit hash, a rebase can be considered. While the CI failure may be a false positive, the CI hasn't been running for some time, so there may be a real issue hiding as well. A rebase triggers the latest CI and makes sure that no silent merge conflicts have snuck in.

@hebasto
Copy link
Member

hebasto commented Jul 30, 2024

Closing due to author's inactivity. Labeled "Up for grabs".

@hebasto hebasto closed this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI failed Up for grabs UX All about "how to get things done"
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants