Elements-qt shows some leftover space in the Overview page after sending assets

Open
#1,143 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop

Research direction

Reproduce the issue in the Elements-qt Overview page by sending assets in their full amount and observing the Available list and Balances area before and after reopening the wallet. Compare the layout after each asset disappears; done means the leftover blank space is removed immediately without restarting the wallet.

Written by the indexing model from the issue text.

Description

GUI

In the Overview page, after sending an asset in its full amount (I mean the value of remaining asset is 0) in which case it disappears from the "Available" list, it seems like the total space in Balances stays the same, leaving a big leftover blank space.
After closing and opening again the wallet it is shown correctly.
Tested on elements 0.21.0.2 and v22.0.0rc2

Example 1 (after having sent various assets in their full amount):
Before closing the wallet:
Before closing the wallet
After reopening the wallet:
After reopening the wallet

Example 2 (after sending 1 asset in its full amount at a time):
After having sent 1 asset:
Screenshot from 2022-08-16 After sending 1 asset in its full amount
After having sent 2 assets:
Screenshot from 2022-08-16 After sending 2 assets in their full amount
After having sent 3 assets:
Screenshot from 2022-08-16 After sending 3 assets in their full amount
After having sent 4 assets:
Screenshot from 2022-08-16 After sending 4 assets in their full amount

Dominant language
C++
Stars
1.2k
Forks
418
Avg merge
1d 23h
Merged PRs (30d)
15

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ElementsProject/elements

All issues in ElementsProject/elements

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.