-
Notifications
You must be signed in to change notification settings - Fork 38.7k
gui: Add transaction record type Fee #12578
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
Conversation
|
Concept ACK, I think it is clearer to list the fee separately. On the other hand, this compounds the issue that it's not possible to see in the list what transaction output records group to one transaction. |
|
@laanwj that's an existing problem isn't? |
Yes, that's what I said. However this compounds it, because it means every transaction will get multiple records, whereas it used to be that this only happens for (rarer) multi-sends. Not an argument against doing this, but something to be aware of, as people will ask "what does this fee belong to". They can find out by looking at the transaction details. |
|
Yeah, in the typical listing it will show an alternating "Fee" row. I was thinking in adding a checkbox to show/hide individual fee rows. Another thing that could help the grouping is to change from alternate rows into "alternate txids", but that is something more complicated to do (as it depends on the proxy model parameters). |
Yeah that can be done in a future PR. Sounds like a good idea.
Might be overkill, just adds an extra configuration that needs to be supported. But no strong opinion. Do add it to the release notes, this is something that users are bound to notice. |
|
Concept ACK. It might (or might not) make sense to only do it for multi-debits... |
8d115aa to
9d6ae2e
Compare
9d6ae2e to
2bbf744
Compare
|
Added release notes. |
|
Concept ACK especially with the grouping (odd/even background alternative). IMO the grouping could be more visible (group entries from a transaction with an outline border line or similar) |
I'll try something along that, but it's not something usual right? |
I guess that is something that could be improved in a follow up PR. |
2bbf744 to
ed5e1c3
Compare
|
Rebased. |
ed5e1c3 to
ae7a25f
Compare
|
Concept ACK |
ae7a25f to
ca5d3d6
Compare
|
Rebased due to conflict in |
ca5d3d6 to
1c778ac
Compare
|
Rebased due to release notes conflict. |
|
Concept ACK |
| } | ||
|
|
||
| public: | ||
| TransactionRecordDelegate(QSortFilterProxyModel* proxy) : m_proxy(proxy) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be explicit :-)
| The last travis run for this pull request was 239 days ago and is thus outdated. To trigger a fresh travis build, this pull request should be closed and re-opened. |
| Needs rebase |
|
Closing for now. The implementation is not ideal anyway. |
Github-Pull: bitcoin/bitcoin bitcoin#12578 Rebased-From: 82dd3e0
Github-Pull: bitcoin/bitcoin bitcoin#12578 Rebased-From: 550f1f3
Github-Pull: bitcoin/bitcoin bitcoin#12578 Rebased-From: 264f9c4
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.
This reverts commit 264f9c4d4f7c1aeb3e89eedddcd88e47e8bba938. This was included in ElementsProject#569 which received no review, and is a backport of upstream PR bitcoin/bitcoin#12578 which was later closed. It leaks memory which is causing CI to fail.


Currently, in the transactions table, the fee is added as debit to the first output. It's a different behaviour from
gettransactionRPC where the values are seen separately:Before:


After:
The row background now alternates based on txid, so in the capture above, the first 3 rows refer to the same transaction.