Update the number of torrents in the filters that are required based on the selected filter #14029

New issue

Open

opened 2026-02-22 00:36:28 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-22 00:36:28 -05:00

Owner

Originally created by @asedii on GitHub (Nov 29, 2022).

Suggestion

Currently, the torrent count in the label of the filters updates entirely based on the properties of all torrents. So for example, if we select a category we still see the same torrent count as they had. I think we should also consider updating the torrent count based on the currently selected filters like categories, tags, and trackers.

Use case

This helps users quickly find out the status of their torrents based on a category, tag, and tracker.

Extra info/examples/attachments

No response

Originally created by @asedii on GitHub (Nov 29, 2022). ### Suggestion Currently, the torrent count in the label of the filters updates entirely based on the properties of all torrents. So for example, if we select a category we still see the same torrent count as they had. I think we should also consider updating the torrent count based on the currently selected filters like categories, tags, and trackers. ### Use case This helps users quickly find out the status of their torrents based on a category, tag, and tracker. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Filters

labels

2026-02-22 00:36:28 -05:00

deekerman commented

2026-02-22 00:36:33 -05:00

Author

Owner

@Kennyh56 commented on GitHub (Nov 29, 2022):

Just downloaded latest software v4.50 , all downloads are inactive. Help!

@Kennyh56 commented on GitHub (Nov 29, 2022): Just downloaded latest software v4.50 , all downloads are inactive. Help!

deekerman commented

2026-02-22 00:36:35 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**