mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Add filter "Active with Traffic" #13518
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#13518
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @itlezy on GitHub (Jun 8, 2022).
Suggestion
Add a filter that displays only the torrents with actual active traffic (download or upload). The bandwidth threshold could be configured eventually.
Use case
Provide a quick way to see what torrents are really "Active"
Extra info/examples/attachments
See commit
github.com/itlezy/qBittorrent@58876dad50@thalieht commented on GitHub (Jun 8, 2022):
I haven't checked if
isActive()is used in any core stuff (and can't be changed because of it). If it is, i would add another method that's intended only for GUI and use that instead for the Active filter. We can't have torrents be considered active solely based on their state e.g. with "Forced" states.@itlezy commented on GitHub (Jun 8, 2022):
Yes, I have added another method
isActiveWTraffic()to keep this logic isolated, see the commit I linked above. I don't have much time to make proper changes and clean commits, so I make changes to my 'experimental' branch and build for me. But someone can take the commit and make it clean to be merged in master@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 ❤
reactionsin 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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)