starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Retain the selection of torrents during navigation through Filters Sidebar #14600

New issue

Open

opened 2026-02-22 01:13:59 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-22 01:13:59 -05:00

Owner

Originally created by @GitHubinatrix on GitHub (May 14, 2023).

qBittorrent & operating system versions

qBittorrent: 4.5.2 x64
Operating system: Windows 10 Enterprise 20H2 x64
Qt: 6.4.2
libtorrent-rasterbar: 2.0.8.0

What is the problem?

Selection of torrent tasks is cancelled when user moves to any entry within Filters Sidebar if that filter is not one of the 4 All ones [STATUS, CATEGORIES, TAGS, TRACKERS] or the one in which user made the selection

In others words: it is impossible to select TORRENT files in one filter and carry it to other and / or back to the first one

Steps to reproduce

1] Go to STATUS > All

2] Select e.g. 5 TORRENT files which names start with letter H [or other from the middle of the alphabet] and which are not yet 100% downloaded

3] Go to STATUS > Downloading

4] Notice how the 5 files still have their selection on them

5] Go back to STATUS > All

6] Notice how the 5 files still have their selection on them

7] Add using CTRL + LEFT MOUSE BUTTON any other TORRENT files to your selection

8] Go to STATUS > Completed

9] Notice how [logically] those 5 first unfinished files are not shown

10] Go back to STATUS > Downloading; - or go to STATUS > All

11] Notice how [unnecessary] nothing of your first and second selection remained active - because it was automatically replaced with focus on the very first file that is accessible in that filter

Additional context

[If this is not a bug but an intented behavior, then please make it at least optionable to retain selection, as for my modus operandi this is just counterproductive and for me personally plain annoying]

Log(s) & preferences file(s)

No response

Originally created by @GitHubinatrix on GitHub (May 14, 2023). ### qBittorrent & operating system versions _qBittorrent: 4.5.2 x64 Operating system: Windows 10 Enterprise 20H2 x64 Qt: 6.4.2 libtorrent-rasterbar: 2.0.8.0_ ### What is the problem? Selection of torrent tasks is cancelled when user moves to any entry within _**Filters Sidebar**_ if that filter is not one of the 4 _**All**_ ones [_**STATUS**_, _**CATEGORIES**_, _**TAGS**_, _**TRACKERS**_] or the one in which user made the selection In others words: it is impossible to select ``TORRENT`` files in one filter and carry it to other and / or back to the first one ### Steps to reproduce 1] Go to _**STATUS > All**_ 2] Select e.g. 5 ``TORRENT`` files which names start with letter H [or other from the middle of the alphabet] and which are not yet 100% downloaded 3] Go to _**STATUS > Downloading**_ 4] Notice how the 5 files still have their selection on them 5] Go back to _**STATUS > All**_ 6] Notice how the 5 files still have their selection on them 7] Add using ``CTRL + LEFT MOUSE BUTTON`` any other ``TORRENT`` files to your selection 8] Go to _**STATUS > Completed**_ 9] Notice how [logically] those 5 first unfinished files are not shown 10] Go back to _**STATUS > Downloading**_; - or go to _**STATUS > All**_ 11] Notice how [unnecessary] nothing of your first and second selection remained active - because it was automatically replaced with focus on the very first file that is accessible in that filter ### Additional context [If this is not a bug but an intented behavior, then please make it at least optionable to retain selection, as for my modus operandi this is just counterproductive and for me personally plain annoying] ### Log(s) & preferences file(s) _No response_

deekerman added the

Feature request

Filters

labels

2026-02-22 01:13:59 -05:00

deekerman commented

2026-02-22 01:14:09 -05:00

Author

Owner

@thalieht commented on GitHub (Feb 13, 2024):

What is all this back and forth? Please write the bare minimum steps to reproduce.

@thalieht commented on GitHub (Feb 13, 2024): What is all this back and forth? Please write the bare minimum steps to reproduce.

deekerman commented

2026-02-22 01:14:10 -05:00

Author

Owner

@GitHubinatrix commented on GitHub (Mar 20, 2024):

What would be the point of reporting a bug a not listing all the steps needed to experience it?

I had written exactly what needs to be done in order to experience it - and confirmed that when executed they will induce it also on a newer version [qBittorrent 4.6.3 x64, Qt: 6.4.3, Libtorrent: Boost: 1.83.0, OpenSSL: 1.1.1w, zlib: 1.3]

@GitHubinatrix commented on GitHub (Mar 20, 2024): What would be the point of reporting a bug a not listing all the steps needed to experience it? I had written exactly what needs to be done in order to experience it - and confirmed that when executed they will induce it also on a newer version [qBittorrent 4.6.3 x64, Qt: 6.4.3, Libtorrent: Boost: 1.83.0, OpenSSL: 1.1.1w, zlib: 1.3]

deekerman commented

2026-02-22 01:14:10 -05:00

Author

Owner

@thalieht commented on GitHub (Mar 20, 2024):

What would be the point of reporting a bug a not listing all the steps needed to experience it?

I had written exactly what needs to be done in order to experience it

Oh yeah? Tell me why exactly you need steps 3-7 then to demonstrate the "bug".

@thalieht commented on GitHub (Mar 20, 2024): >What would be the point of reporting a bug a not listing all the steps needed to experience it? > >I had written exactly what needs to be done in order to experience it Oh yeah? Tell me why exactly you need steps 3-7 then to demonstrate the "bug".

deekerman commented

2026-02-22 01:14:10 -05:00

Author

Owner

@GitHubinatrix commented on GitHub (Apr 23, 2024):

But of course to be able to notice how the 5 files still have their selection on them

@GitHubinatrix commented on GitHub (Apr 23, 2024): But of course to be able to notice how the 5 files still have their selection on them

deekerman commented

2026-02-22 01:14:10 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 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 25, 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.)**