mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Portability #2550
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#2550
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 @mneTG on GitHub (May 24, 2015).
Why the need to store configuration in local user directories. I lose torrents if windows crashes and need to be reinstalled. Vuze isn't like that.
@chrishirst commented on GitHub (May 25, 2015):
Because the QT frameworks uses 'native' operating system functions and each OS has defined locations for storing user setting and configuration
As you know where the configuration files are stored, keep a maintained backup external to the OS. That method should always be 'Plan A' for any Windows user.
@mneTG commented on GitHub (May 29, 2015):
That is if you follow the Microsoft guidelines for software dev.
That backup can be big some times. and I believe in software portability.
@chrishirst commented on GitHub (May 29, 2015):
Which QT does by using native OS functions
What? The configuration files??? Big??? Maybe if a few hundred thousand tasks were loaded the folder might creep over a few tens of MiB
Then you should understand WHY 'native' OS functions ARE used for cross platform 'portability'.
@zeule commented on GitHub (Jan 13, 2017):
Duplicate of #465