Load and store torrent file info in memory. #164

New issue

Open

opened 2026-02-21 14:54:58 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 14:54:58 -05:00

Owner

Originally created by @Zealotus on GitHub (Oct 24, 2012).

So I've set my browser to clear chace and temporary files upon closing...
And earlier I was adding a lot of torrents but left them at the "Select download destination"-window.
So when I was done browsing I closed my browser and started activating the torrents.
However none of them showed up in the download list...

So I made a test to see if this was actually the case:
Opened my broser again, fetched some torrents, left them at select destination, closed browser, clicked OK for each torrent. Again, none showed up...

Originally created by @Zealotus on GitHub (Oct 24, 2012). So I've set my browser to clear chace and temporary files upon closing... And earlier I was adding a lot of torrents but left them at the "Select download destination"-window. So when I was done browsing I closed my browser and started activating the torrents. However none of them showed up in the download list... So I made a test to see if this was actually the case: Opened my broser again, fetched some torrents, left them at select destination, closed browser, clicked OK for each torrent. Again, none showed up...

deekerman added the

Feature request

label

2026-02-21 14:54:58 -05:00

deekerman commented

2026-02-21 14:55:01 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Dec 5, 2012):

Hmm, I think the real solution will be for qbt to lock the file when it opens it for reading so noone can delete it before you decide what to do with it.

@sledgehammer999 commented on GitHub (Dec 5, 2012): Hmm, I think the real solution will be for qbt to lock the file when it opens it for reading so noone can delete it before you decide what to do with it.

deekerman commented

2026-02-21 14:55:03 -05:00

Author

Owner

@Zealotus commented on GitHub (Dec 5, 2012):

Or that, yes, better idea! Didn't think so far ;P

@Zealotus commented on GitHub (Dec 5, 2012): Or that, yes, better idea! Didn't think so far ;P

deekerman commented

2026-02-21 14:55:03 -05:00

Author

Owner

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

Rows
Columns