Skip to content

Conversation

@promag
Copy link
Contributor

@promag promag commented Mar 1, 2018

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

gettransaction 56d4c03f65f32acecd80ec6ec1b5cd12eddcd35d705f2d4c82a90c85b1cf872a

{
  ...
  "details": [
    {
      "account": "",
      "address": "2N3AFooPuYvN6zWPpThPB8w8V48Ph31PuKH",
      "category": "send",
      "amount": -1,
      "label": "",
      "vout": 0,
      "fee": -0.0000022,
      "abandoned": false
    },
    {
      "account": "",
      "address": "2N42JYZHhwRXgrpuztod6CcEXfUDLTqbhY7",
      "category": "send",
      "amount": -1,
      "label": "",
      "vout": 1,
      "fee": -0.0000022,
      "abandoned": false
    }
  ],
  ...
}

Before:
screen shot 2018-03-01 at 18 44 20
After:
screen shot 2018-03-06 at 13 55 08
The row background now alternates based on txid, so in the capture above, the first 3 rows refer to the same transaction.

@fanquake fanquake added the GUI label Mar 1, 2018
@laanwj
Copy link
Member

laanwj commented Mar 5, 2018

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.

@promag
Copy link
Contributor Author

promag commented Mar 5, 2018

@laanwj that's an existing problem isn't?

@laanwj
Copy link
Member

laanwj commented Mar 5, 2018

@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.

@promag
Copy link
Contributor Author

promag commented Mar 5, 2018

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).

@laanwj
Copy link
Member

laanwj commented Mar 5, 2018

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.
I wonder how that will/should interact with sorting on alternative columns, though.

I was thinking in adding a checkbox to show/hide individual fee rows.

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.

@luke-jr
Copy link
Member

luke-jr commented Mar 5, 2018

Concept ACK. It might (or might not) make sense to only do it for multi-debits...

@promag promag force-pushed the 2018-03-fee-transaction-record branch from 8d115aa to 9d6ae2e Compare March 6, 2018 13:56
@promag
Copy link
Contributor Author

promag commented Mar 6, 2018

@laanwj I've implemented alternating rows based on transaction id (see after image above). The implementation is not efficient but it's enough to evaluate the concept.

@luke-jr even for single-debit it's weird to have the fee associated to that address, sounds like you sent that value there.

@promag promag force-pushed the 2018-03-fee-transaction-record branch from 9d6ae2e to 2bbf744 Compare March 6, 2018 20:06
@promag
Copy link
Contributor Author

promag commented Mar 6, 2018

Added release notes.

@jonasschnelli
Copy link
Contributor

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)

@promag
Copy link
Contributor Author

promag commented Apr 12, 2018

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?

@jonasschnelli
Copy link
Contributor

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.

@promag promag force-pushed the 2018-03-fee-transaction-record branch from 2bbf744 to ed5e1c3 Compare April 13, 2018 20:59
@promag
Copy link
Contributor Author

promag commented Apr 13, 2018

Rebased.

@promag promag force-pushed the 2018-03-fee-transaction-record branch from ed5e1c3 to ae7a25f Compare April 13, 2018 21:06
@maflcko maflcko changed the title Add transaction record type Fee gui: Add transaction record type Fee May 10, 2018
@laanwj
Copy link
Member

laanwj commented May 10, 2018

Concept ACK

@jonasschnelli
Copy link
Contributor

@jonasschnelli
Copy link
Contributor

Tested ACK ae7a25fafc08482ba8af2174c3e8002bbe5a3bac

Before / After:

bildschirmfoto 2018-05-14 um 08 26 42

bildschirmfoto 2018-05-14 um 08 27 56

@promag promag force-pushed the 2018-03-fee-transaction-record branch from ae7a25f to ca5d3d6 Compare May 24, 2018 15:46
@promag
Copy link
Contributor Author

promag commented May 24, 2018

Rebased due to conflict in src/qt/test/wallettests.cpp.

@promag promag force-pushed the 2018-03-fee-transaction-record branch from ca5d3d6 to 1c778ac Compare June 24, 2018 15:05
@promag
Copy link
Contributor Author

promag commented Jun 24, 2018

Rebased due to release notes conflict.

@jb55
Copy link
Contributor

jb55 commented Aug 24, 2018

Concept ACK

}

public:
TransactionRecordDelegate(QSortFilterProxyModel* proxy) : m_proxy(proxy) {}
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be explicit :-)

@DrahtBot DrahtBot closed this May 7, 2019
@DrahtBot
Copy link
Contributor

DrahtBot commented May 7, 2019

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.

@DrahtBot
Copy link
Contributor

DrahtBot commented May 9, 2019

Needs rebase

@promag
Copy link
Contributor Author

promag commented Jun 30, 2019

Closing for now. The implementation is not ideal anyway.

@promag promag closed this Jun 30, 2019
kallewoof pushed a commit to kallewoof/bitcoin that referenced this pull request Oct 4, 2019
kallewoof pushed a commit to kallewoof/bitcoin that referenced this pull request Oct 4, 2019
Github-Pull: bitcoin/bitcoin bitcoin#12578
Rebased-From: 550f1f3
kallewoof pushed a commit to kallewoof/bitcoin that referenced this pull request Oct 4, 2019
Github-Pull: bitcoin/bitcoin bitcoin#12578
Rebased-From: 264f9c4
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 12, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 13, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 14, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 14, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 14, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 14, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 16, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 16, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Dec 16, 2020
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.
apoelstra added a commit to apoelstra/elements that referenced this pull request Mar 26, 2021
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.
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants