Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[QOL] show allocated GB before, allocated GB after, GB saved in the watched folders Tab instead of only GB saved

Open
#626 0 comments 4 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
visualbasic
Domain
desktop

Research direction

Find the implementation of the Watched Folders tab and inspect how its compression progress bar and hover text are populated. Define the displayed before, after, and saved values, then investigate the requested name/status sorting or search behavior; the work is done when the tab shows the values persistently and supports the selected navigation improvement.

Written by the indexing model from the issue text.

Description

First of all, thanks for the great work! I have a suggestion for a Quality of Lifei mprovement.

Currently, in the 'Watched Folders' tab, the decayed status is shown as a progress bar along with a percentage text. When hovering over it, it displays how much storage space has been saved.

My suggestion would be to keep the bar for a quick visual overview, but change the permanent text (regardless of hovering) to show: Allocated GB before compression, Allocated GB after, and GB saved.

Additionally, it would be very useful if the 'Watched Folders' tab could be sorted by name or decayed status, or if a search field could be added.

Thanks again for the amazing work.

Dominant language
Visual Basic .NET
Stars
8.9k
Forks
343
Avg merge
3d 18h
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 IridiumIO/CompactGUI

All issues in IridiumIO/CompactGUI

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.