[Gui] Transaction History becomes cluttered after rainbymagnitude

[NetherStar64]

After doing a rainbymagnitude, the transaction list in the gui is cluttered with many small transactions. It would look better if e.g. it was in a single entry

[jamescowens]

This cannot be supported right now, because a rain transaction is currently essentially a regular transaction that has a lot of outputs. There is no separate contract for rain, and so there is no programmatic way to distinguish between a regular transaction and a rain. If we decide to create a contract for rain, which is likely, I will revisit this, but I am skeptical, because the request violates the rules that the transaction lists each payee in a send transaction separately so you have a visible record of where the funds went to.

[jamescowens]

I have decided to leave this open as a feature request for discussion.

[RoboticMind]

... the request violates the rules that the transaction lists each payee in a send transaction separately so you have a visible record of where the funds went to.

Perhaps it could instead have a expand/contract button on the transaction instead? Although that might cause big performance issues with hundreds of transactions

[jamescowens]

That is probably not workable... and it is not worth the effort for this corner-case.

[NetherStar64]

Maybe display one transaction in the list with a rain Icon and list the Addresses and Amount sent in the transaction details

[jamescowens]

It already is in the details. The issue is being able to special case this situation to NOT display the details for a rain in the transaction grid. This cannot be done without rain being implemented with a rain contract to be able to distinguish between a rain and an ordinary transaction.

[jamescowens]

There is a complicated decomposition function that maps between core transactions and the displayed transactions in the GUI. In general, the core transactions are much more coarse-grained. One core transaction maps to one or more displayed transaction rows depending on nature of the transaction.