It's no biggie. We have a policy to give primary status to natively portable programs but if this item is in flux, I don't mind waiting for the dust to settle.Userfriendly wrote:Maybe? Maybe not? I'm not even sure if relative file paths is necessary unless users run qbittorrent and save files on the same USB drive and plan to seed it later on a different computer.
Submit portable freeware that you find here. It helps if you include information like description, extraction instruction, Unicode support, whether it writes to the registry, and so on.
histisev wrote: ↑Tue Jan 03, 2017 2:43 amFor the love of all that's holy at Portable Freeware, REMOVE this app. It is NOT portable. When it associates with magnet files it spreads its crap all over the computer. Legions of users have begged the author to institute true portable mode, but he's demanding money.
It's ironic. Portable & freeware... two of which are features not inherent to this problem.
I along with many other users have reverted to uTorrent 2.2.1 until this dev stops being such an ass to its loyal base.
may i know what kind files does it spread?
&This app should be reported and removed from PF as it constantly spreads its files all over my computer after magnet links are associated.
and does somebody deeply tested it ?I gave qbittorrent an honest try. I can't get magnet links to associate with the portable version anymore. I even tried running it in Sandboxie and manually installing a reg entry.
does it spread files ?
He means it will still use standard windows AppData directories for settings when you associate and open torrent files and magnet links. At least thats how it should work if not in portable mode. But In my case, it actually decided to leave settings in my portable Firefox app folder and in System32! Since qBittorrent requires command line switch or environment variable to have its settings "portable", having portable settings and file and magnet link association isn't possible at the moment because of how portable mode works.
https://github.com/qbittorrent/qBittorrent/issues/7769 Using the Env Var QBT_PROFILE or QBT_PORTABLE should help keep qBittorrent using portable settings without command line switches through shortcuts or launchers so you can open associated torrent files and magnet links directly and settings stay portable. But it just doesn't work as it should.
qBittorrent should be able to automatically be able to go portable mode if it recognizes settings files in executable directory like any other well done portable apps do. None of this cmd args or custom launchers should be necessary. Its why I still use utorrent as my primary torrent app for opening torrent files and magnet links since it can still have windows recognize it as my default app for opening that stuff and still keeps its settings working portably.
All that disussion and work to make it work portable natively and they somehow manage to do a janky implementation of it boggles me. I understand that file association isn't normally what you would thing you would be using with portable apps in mind but a lot of portable apps out there work well with it otherwise. Not the case with qBittorrent. It's either full install mode or whatever the developer thinks portable mode is limited to. https://github.com/qbittorrent/qBittorrent/issues/7236
Other related portable mode issue https://github.com/qbittorrent/qBittorrent/issues/7765
thank you so much , i was worried after reading
. Seriously, if you think this is an opinion go read the issues forum. as ransom for portable mode, he's demanding people give him money. You really can't make this sh##t up.
Well yeah its supported that for awhile now. loin2kolpotoru a little late on that news. The issue with --portable still exists. I/O errors after saving files in same drive as qbittorrent executable and restarting client. Still preferable to use --profile=profile to avoid it. See https://github.com/qbittorrent/qBittorrent/issues/7765
Other portable related issue associating .torrent files with QBT_PROFILE or QBT_PORTABLE env variables. Its not standard practice to use env variables to configure portable mode for apps but its an option for qbittorrent to force where it reads/saves its settings. See https://github.com/qbittorrent/qBittorrent/issues/7770 and https://github.com/qbittorrent/qBittorrent/issues/7769
Probably still better to keep using portable launcher. Just easier for most users. The current portable implementation is not perfect and it still requires using shortcut link, batch file, env variable or some other launcher to use the command line parameter. It seems to be a low priority issue. Wouldn't hold out hope for it to be improved upon anytime soon.