The layout is quite messy, which makes it ahrd to see what's going on (and thus easy to overlook some problem). IMHO it would be a lot easier to comprehend if the information was structured like this:
fanquake added the label GUI on Nov 4, 2017
MarcoFalke
commented at 4:10 PM on November 4, 2017:
member
The layout is quite messy, which makes it ahrd to see what's going on (and
thus easy to overlook some problem). IMHO it would be a lot easier to
comprehend if the information was structured like this:
shashisamala
commented at 7:47 PM on November 4, 2017:
none
lgtm
Sjors
commented at 5:59 AM on November 5, 2017:
member
Good improvement.
I woud leave out "added" and capitalize the first word.
To make it more clear that users pay per (v)byte, you could also change it to "Transaction fee for 0.168 kB".
Perhaps a separate change, but you could show the fee as a percentage, in small font under the fee.
flack
commented at 10:52 AM on November 6, 2017:
contributor
Yes, I agree that "added" is superfluous and can be removed (also i made a little error when I copied your RBF text, so it's not intended to be different from what you proposed in #11556). I'm also wondering if the "= 1.08400 mBTC.." line shouldn't rather go in the right column (underneath the total sum), but those are details that can be worked out once someone actually codes this :-)
laanwj added the label help wanted on Nov 8, 2017
gmverdon
commented at 3:54 PM on November 10, 2017:
none
Based on the design of @flack, but with a few adjustments.
MarcoFalke
commented at 3:59 PM on November 10, 2017:
member
Feel free to create a pull request for this. I think we can fine tune the nits later, but the general design seems a good way to go.
flack
commented at 4:00 PM on November 10, 2017:
contributor
@gmverdon what would it look like if you send to more than one address?
gmverdon
commented at 5:51 PM on November 10, 2017:
none
@flack that is a good one, haven't thought of that possibility yet. The solution you provided is indeed more elegant when sending to more than one address.
jnewbery
commented at 8:31 PM on March 27, 2018:
member
@flack@gmverdon - do either of you plan to open a PR for this?
If not, I suggest we close this as stale.
flack
commented at 8:37 PM on March 27, 2018:
contributor
@jnewbery nah, I'm good. I was actually thinking about suggesting giving stuff like this a "good first issue" tag, because it's pretty self-contained and you don't need to know a lot about the code to work on it, but do whatever fits your workflow
jnewbery
commented at 8:47 PM on March 27, 2018:
member
Thanks @flack . Generally I think it's better to close out WIBNI issues rather than let them sit for months or years.
ryanofsky
commented at 8:59 PM on March 27, 2018:
member
flack
commented at 4:00 PM on May 15, 2018:
contributor
@marcoagner true, it actually is a duplicate of #10613, didn't see this one before :-)
Your version in #13158 is definitely a readability improvement, although I have to say that for me, the point of both tickets is more to get the numbers all aligned into one column, so that it's easier to check the math by adding them:
Description
Amount
some address
14.200101
Transaction fee (0.123 kB)
0.200010
Total Amount
14.400111
is way easier to manually check than
14.200101 to
some address
Transaction fee (0.123 kB): 0.200010
Total Amount: 14.400111
MarcoFalke
commented at 4:06 PM on May 15, 2018:
member
I attempted to achieve that with a span style=float:left for the left column and a span style=float:right for the right column, but it appeared as if the style was ignored. Feel free to fix this up @flack or @marcoagner, but I think it is not worth keeping this issue open.
flack
commented at 4:16 PM on May 15, 2018:
contributor
@MarcoFalke looks like float is only supported on tables and images according to http://doc.qt.io/archives/qt-4.8/richtext-html-subset.html#css-properties . If the individual lines were wrapped in p or div, align=right should work, although the cleanest version would probably be to convert the dialog to use <table>. At some point, I might try to implement this, but don't hold your breath :-) (also, I'm very happy if someone beats me to it!)
marcoagner
commented at 4:21 PM on May 15, 2018:
contributor
In my opinion, the alignment of numbers to the right side-by-side with addresses gets tricky if the addresses are not truncated and I don't think the addresses should be truncated here. But, in case anybody decides to work on this in the future, what @flack commented holds (same behavior qt5) and <table> will probably be the way to go.
flack
commented at 4:27 PM on May 15, 2018:
contributor
If truncation is the issue (could be mitigated with a tooltip showing the full address if that's deemed acceptable), then an alternative might be something like this:
To: somereallyreallylongaddresswewanttoseecompletelywithoutanytruncation
14.20330393 BTC
Transaction fees (0.122 kB)
0.20000000 BTC
Total Amount:
14.40330393 BTC
The advantage is that this should be doable without tables, i.e. simply with <p> tags, the drawback is that it uses more vertical space
fanquake removed the label Up for grabs on Mar 21, 2019
jasonbcox referenced this in commit 6b6d0ee541 on Oct 11, 2019
UdjinM6 referenced this in commit ee8beba049 on Jun 18, 2021
TheArbitrator referenced this in commit 52ad4ff0ab on Jun 21, 2021
UdjinM6 referenced this in commit 9316725eb2 on Jun 24, 2021
UdjinM6 referenced this in commit d8051ec52f on Jun 29, 2021
UdjinM6 referenced this in commit 47b2895954 on Jun 29, 2021
UdjinM6 referenced this in commit 9621d4181b on Jul 2, 2021
UdjinM6 referenced this in commit 984f6bbd18 on Jul 4, 2021
UdjinM6 referenced this in commit a650372830 on Jul 6, 2021
This is a metadata mirror of the GitHub repository
bitcoin/bitcoin.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2026-04-14 21:15 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me