You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I open this as tracking issue for transaction and payment export features, as we have already talk internally, the work will be split in 2 steps:
I and @pythcoiner were discussing about the tx/payments export functionality and we reached the following proposal: we could divide the activity in two steps:
Produce an "Export Transactions data" functionality which would be in the "Transactions" tab and would simply export the data of the transactions (TxId, Blockheight, Date, Label, Value, Fee)
Use the work of step 1 to produce a more complex "Export Payments data" functionality in Home page that would include all the data we were discussing last week.
The division in two steps shouldn't imply much more work and should make it more likely to have at least step 1 for v9. Also, having the tx export too could be good for people/businesses who have already automated systems based on this kind of data instead of payments. Any comment or counter argument to such approach?
According to what we discussed yesterday, for the moment we won't review much the UX for the background process management. This will be part of an entire UX review activity, valid for all such processes (e.g. rescan, export, syncing...). We will still need a way to manage the possibility of it going longer than expected (timeout? "cancel" button?).
for now i think we should lock the screen navigation w/ cancel + timeout mechanism, it appear to me the most easy to implement as we can easyly do it with a subscription at the panel level.
I open this as tracking issue for transaction and payment export features, as we have already talk internally, the work will be split in 2 steps:
link to previous discussion
The text was updated successfully, but these errors were encountered: