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

Add more columns to the transaction list in the GUI #10369

Closed
GSPP opened this issue May 9, 2017 · 4 comments
Closed

Add more columns to the transaction list in the GUI #10369

GSPP opened this issue May 9, 2017 · 4 comments

Comments

@GSPP
Copy link

GSPP commented May 9, 2017

On big screens the transaction list has a lot of space that is not utilized:

image

I suggest that the columns shown here are made configurable. I would personally like the following columns:

  • Debit
  • Fee
  • Net amount
  • TxID
  • Number of recipients
  • Number of inputs
  • Number of confirmations (right now this is rendered as a graphical indicator combined with a tooltip)
  • A button column "Copy transaction details to clipboard". This is useful for copying out all of the data to document the transaction in some other place.
  • Maybe a text comment for the transaction in addition to the label (which is meant to be short)

I am always unsure what the "Amount (BTC)" column means. It would help to have all three amount-based columns available. Right now I have to open the transaction details to find those values.

Maybe there are other data that can be exposed for power users as well.

@jonasschnelli
Copy link
Contributor

I'm not sure if the amount of columns can depend on the window-width. Adding more column for "standard" window-widths may result into confusion.
However, I think this approach should by tried out...

@ghost
Copy link

ghost commented May 17, 2017

How about an option to enable/disable each extra column, but keep these disabled by default? @jonasschnelli

@GSPP
Copy link
Author

GSPP commented May 20, 2017

@laudaa that's what I meant.

@maflcko
Copy link
Member

maflcko commented Apr 26, 2020

The feature request didn't seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open issues.

Closing due to lack of interest. Pull requests with improvements are always welcome.

@maflcko maflcko closed this as completed Apr 26, 2020
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants