Every program has its differences and learning curves. Once you get used to it (and at the end know it) I don't see any problems with it.
As I said earlier; There are only 2 buttons. Resume/Pause speaks for itself. I don't know why someone would get confused. If you going to compare it with other clients and what they do with it then you will get confused by yourself. I've used nearly all torrenting clients in the past and all have their differences. On the private tracker that im using thousands of users are using qBittorrent and they never complained about it (if you know how strict, picky they sometimes can be about little things).
I do understand it till a certan degree, but its nothing big to worry about.
If pause is really stop, why call it pause?
-
ciaobaby
Re: If pause is really stop, why call it pause?
The "Pause" makes perfect sense because you are actually pausing the task, ie; the task is halted where it is and that state is held until resumed, just like a CD, DVD, Video, MP3 player etc is when you pause one of those. The computer analogy is 'suspend', where the state of running tasks are saved, the system is 'paused' until it is resumed when it leaves suspension.
Stop, on the other hand implies the task is ended and restarts from the beginning just as a CD, DVD, Video, MP3 etc. etc. does when a stop event is actioned.
Stop, on the other hand implies the task is ended and restarts from the beginning just as a CD, DVD, Video, MP3 etc. etc. does when a stop event is actioned.
-
sledgehammer_999
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: If pause is really stop, why call it pause?
And to expand on what ciaobaby said:
Take for example the regular download managers or even the simple builtin one in firefox. If you pause a download it drops the connections but it is ready to continue from where you left of(assuming the server supports resumes). If you hit stop and then resume the download starts from the beginning and all downloaded data are discarded.
Take for example the regular download managers or even the simple builtin one in firefox. If you pause a download it drops the connections but it is ready to continue from where you left of(assuming the server supports resumes). If you hit stop and then resume the download starts from the beginning and all downloaded data are discarded.
-
Switeck
Re: If pause is really stop, why call it pause?
I too am of the opinion that the Pause in qBT should be relabeled Stop.
Maybe a little late in the game to make that change, but this is for the sake of new users and their first impressions...especially those migrating from uTorrent/BitTorrent which has/had a separate Pause/Stop functionality.
Maybe a little late in the game to make that change, but this is for the sake of new users and their first impressions...especially those migrating from uTorrent/BitTorrent which has/had a separate Pause/Stop functionality.
-
hyperion1is
Re: If pause is really stop, why call it pause?
[quote="ciaobaby"]
The "Pause" makes perfect sense because you are actually pausing the task, ie; the task is halted where it is and that state is held until resumed, just like a CD, DVD, Video, MP3 player etc is when you pause one of those. The computer analogy is 'suspend', where the state of running tasks are saved, the system is 'paused' until it is resumed when it leaves suspension.
Stop, on the other hand implies the task is ended and restarts from the beginning just as a CD, DVD, Video, MP3 etc. etc. does when a stop event is actioned.
[/quote]
Actually this explanation does makes sense. You are right. A torrent is paused and then resumes from where it was left. If the torrent was stopped would resume from beginning.
This should be put in FAQ https://github.com/qbittorrent/qBittorr ... -Questions (I know it may appear simple but how you can see other user may bother you with this). And a suggestion, FAQ should be a submenu of Help in Qbt since newbies will prefer that instead of Documentation which sounds technical.
Also, I'm not quite clear about the difference from pause in other torrents and qBt. In Utorrent I think there is a difference between Stop and Pause. On Pause, if I remember right, the download was stopped but the upload continued. And Stop dl and up where stopped.
In qBt when I hit Pause everything (for that torrent) stops? In the sense, that it has no activity and no Cpu or other resources will be used (for that specific torrent, not qBt in general)?
Ofcourse this also should be in FAQ. A humble opinion.
The "Pause" makes perfect sense because you are actually pausing the task, ie; the task is halted where it is and that state is held until resumed, just like a CD, DVD, Video, MP3 player etc is when you pause one of those. The computer analogy is 'suspend', where the state of running tasks are saved, the system is 'paused' until it is resumed when it leaves suspension.
Stop, on the other hand implies the task is ended and restarts from the beginning just as a CD, DVD, Video, MP3 etc. etc. does when a stop event is actioned.
[/quote]
Actually this explanation does makes sense. You are right. A torrent is paused and then resumes from where it was left. If the torrent was stopped would resume from beginning.
This should be put in FAQ https://github.com/qbittorrent/qBittorr ... -Questions (I know it may appear simple but how you can see other user may bother you with this). And a suggestion, FAQ should be a submenu of Help in Qbt since newbies will prefer that instead of Documentation which sounds technical.
Also, I'm not quite clear about the difference from pause in other torrents and qBt. In Utorrent I think there is a difference between Stop and Pause. On Pause, if I remember right, the download was stopped but the upload continued. And Stop dl and up where stopped.
In qBt when I hit Pause everything (for that torrent) stops? In the sense, that it has no activity and no Cpu or other resources will be used (for that specific torrent, not qBt in general)?
Ofcourse this also should be in FAQ. A humble opinion.
-
ciaobaby
Re: If pause is really stop, why call it pause?
The uTorrent 'pause' is where transfer is halted but peer connections are maintained by sending "keep-alive" messages to peers and/or ignoring/discarding piece requests from peers this behaviour can lead to being blocked by some clients.
Which is the very definition of the noun pause.
, Exactly. In a state of hiatus ie: a temporary cessation of activity.In the sense, that it has no activity and no Cpu
Which is the very definition of the noun pause.
Absolutely! There are many things that should be in what passes for a 'manual'/'help'/'documentation'/user 'reference', that is one place that the less/non technical qBT users can get involved, it is a very low priority for the active developers but that shouldn't mean a low priority for everyone. Hey, I'll donate the hosting for it if anyone wants to be involved.Ofcourse this also should be in FAQ
-
sledgehammer_999
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: If pause is really stop, why call it pause?
[offtopic]The wiki is freely editable by anyone registered on github[/offtopic]
-
hyperion1is
Re: If pause is really stop, why call it pause?
[quote="sledgehammer_999"]
[offtopic]The wiki is freely editable by anyone registered on github[/offtopic]
[/quote]
OK. I will take a look.
@ciaobaby
You will donate the hosting for what? Something different than the FAQ on github?
[offtopic]The wiki is freely editable by anyone registered on github[/offtopic]
[/quote]
OK. I will take a look.
@ciaobaby
You will donate the hosting for what? Something different than the FAQ on github?
-
ciaobaby
Re: If pause is really stop, why call it pause?
Something that is bit more of a cohesive manual than the disparate "developers notebook" bunch of 'pages' that is the Git Wiki. Let's be honest it's more of a "how to make things for qBT" guide than it is a "how to use qBitTorrent" guide. The average user wants to know "what happens when I do [this]" not how to "Compile qBT on Mac OSX".
I would think that for the majority of users, "compilation" is just another way of describing a "Best of" CD and "dynamic linkage" is what connects the pedals to the rear wheel of their push bike.
I would think that for the majority of users, "compilation" is just another way of describing a "Best of" CD and "dynamic linkage" is what connects the pedals to the rear wheel of their push bike.
-
sledgehammer_999
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: If pause is really stop, why call it pause?
[quote="ciaobaby"]
Something that is bit more of a cohesive manual than the disparate "developers notebook" bunch of 'pages' that is the Git Wiki. Let's be honest it's more of a "how to make things for qBT" guide than it is a "how to use qBitTorrent" guide. The average user wants to know "what happens when I do [this]" not how to "Compile qBT on Mac OSX".
I would think that for the majority of users, "compilation" is just another way of describing a "Best of" CD and "dynamic linkage" is what connects the pedals to the rear wheel of their push bike.
[/quote]
You can always do that in github wiki. Create a new page "user manual" and then subpages according to your desired layout of the guide.
Something that is bit more of a cohesive manual than the disparate "developers notebook" bunch of 'pages' that is the Git Wiki. Let's be honest it's more of a "how to make things for qBT" guide than it is a "how to use qBitTorrent" guide. The average user wants to know "what happens when I do [this]" not how to "Compile qBT on Mac OSX".
I would think that for the majority of users, "compilation" is just another way of describing a "Best of" CD and "dynamic linkage" is what connects the pedals to the rear wheel of their push bike.
[/quote]
You can always do that in github wiki. Create a new page "user manual" and then subpages according to your desired layout of the guide.
-
ciaobaby
Re: If pause is really stop, why call it pause?
Well let's go for it then, I use my real name on Git but don't let that put anyone off.
-
zeomal
Re: If pause is really stop, why call it pause?
On the issue of the pause button, I was pretty much relieved when the pause button actually did as advertised. On µTorrent, the activity of the torrent never ceased.
How about creating a simple wiki that contains all the beginners information, like "What are torrents?" and stuff, then moving on to "How to use qBittorrent? (basic)" and "How to use qBittorrent? (advanced)?"?
I haven't ever used Github, but I'll be happy to create an account for making a wiki for the casual first time user.
Shouldn't I first present a draft of the wiki? If yes, where? (I know, I'm NOT involved in coding, so that's the reason for the stupid questions.)
So, we are free to create a How to use qBittorrent wiki on Github? In fact, me being less involved in coding, I can pretty much resonate with a lot of normal users. So can hyperion1is.You can always do that in github wiki. Create a new page "user manual" and then subpages according to your desired layout of the guide.
How about creating a simple wiki that contains all the beginners information, like "What are torrents?" and stuff, then moving on to "How to use qBittorrent? (basic)" and "How to use qBittorrent? (advanced)?"?
I haven't ever used Github, but I'll be happy to create an account for making a wiki for the casual first time user.
Shouldn't I first present a draft of the wiki? If yes, where? (I know, I'm NOT involved in coding, so that's the reason for the stupid questions.)
Last edited by zeomal on Wed Jul 09, 2014 5:26 pm, edited 1 time in total.
-
sledgehammer_999
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: If pause is really stop, why call it pause?
I don't want to be in charge of the manual/user guide. Just create an account on github and create a page/link on the first wiki page reading "User Guide" or "Use manual" and then start populating that page with info, subpages, whatever.
If you want to organize somehow with other users (eg ciaobaby), you should create a separate forum thread. Don't continue the wiki discussion in this one.
If you want to organize somehow with other users (eg ciaobaby), you should create a separate forum thread. Don't continue the wiki discussion in this one.
-
armando_rod
Re: If pause is really stop, why call it pause?
Long time uTorrent user here.
If the "pause" button does the same as "stop" on uTorrent then it shouldnt check for the file on the HDD every time qbt is opened, is anoying that I "pause" a torrent delete the file and the torrent is kept in the same number que and in 0% RED.
If I stop a torrent I'm sure that I no longer need it on the queue, it should be place last regardless the file exist or not in the HDD. Right now if I delete a file on the paused torrents the next time I open qbt the torrent get placed in the queue again.
If the "pause" button does the same as "stop" on uTorrent then it shouldnt check for the file on the HDD every time qbt is opened, is anoying that I "pause" a torrent delete the file and the torrent is kept in the same number que and in 0% RED.
If I stop a torrent I'm sure that I no longer need it on the queue, it should be place last regardless the file exist or not in the HDD. Right now if I delete a file on the paused torrents the next time I open qbt the torrent get placed in the queue again.
-
ciaobaby
Re: If pause is really stop, why call it pause?
It will only do that if you close qBT without allowing it to shutdown cleanly.If the "pause" button does the same as "stop" on uTorrent then it shouldnt check for the file on the HDD every time qbt is opened,
For that you would use the [X Delete] button.If I stop a torrent I'm sure that I no longer need it on the queue,
Something like this >> https://github.com/qbittorrent/qBittorrent/issues/1820 ??Right now if I delete a file on the paused torrents the next time I open qbt the torrent get placed in the queue again.
The same questions apply also.