If pause is really stop, why call it pause?

Discuss suggestions and ideas for the forums, site, software.
armando_rod

Re: If pause is really stop, why call it pause?

Post by armando_rod »

I'm exiting the progrma via the [X] button on upper right.

Look this screenshot, the first files are torrents that I paused and then deleted/moed the files (once I open qbt it check and put the torrent again on the queue as paused but 0%. The second set of files are torrents that I havent deleted from HDD they stay on a finished state (100%) and paused normally UNTIL I delete files or move files to other location,

Screenshot http://imgur.com/4yPNnmt
ciaobaby

Re: If pause is really stop, why call it pause?

Post by ciaobaby »

I'm exiting the progrma via the [X] button on upper right.
That may only close the GUI window, NOT the whole application.
that I paused and then deleted/moed the files (once I open qbt it check and put the torrent again on the queue as paused but 0%..
.
What exactly do you expect to happen when you delete the payload from the drive so qBT cannot actually find any of it???
If somebody removed all the beer from your fridge to the rubbish bin, wouldn't YOU think that your beer supply was at 0% when you checked???
The second set of files are torrents that I havent deleted from HDD they stay on a finished state (100%) and paused normally UNTIL I delete files or move files to other location,
Seeding files do NOT have a queue number, never have, never will do.
armando_rod

Re: If pause is really stop, why call it pause?

Post by armando_rod »

What exactly do you expect to happen when you delete the payload from the drive so qBT cannot actually find any of it???
If somebody removed all the beer from your fridge to the rubbish bin, wouldn't YOU think that your beer supply was at 0% when you checked???.
.

Nothing, thats why I said IF "pause" = "stop" on uTorrent then it should stop the torrent, no checks no nothing! Thats what I expect.

If I stop taking beer of the fridge well I cant be aware if there are beers or not.

In my opinion there should be a button labled STOP that stop the torrent completlly never check for anything on that torrent it shouldnt care if the files are gone or not but thats my opinion as a uTorrent user since v2.0.
sledgehammer_999
Administrator
Administrator
Posts: 2443
Joined: Sun Jan 23, 2011 1:17 pm

Re: If pause is really stop, why call it pause?

Post by sledgehammer_999 »

First of all qBittorrent isn't utorrent.
Secondly, when a torrent is stopped in utorrent and you delete manually the files, utorrent doesn't pick up the change. It doesn't care. The story is different with qBittorrent. It does check if the files are there even when paused. I don't intend to change that.
The difference is that utorrent continues to show 100% (which is false), but qBittorrent shows 0%(which is true). I think qBittorrent does the right thing here.
armando_rod

Re: If pause is really stop, why call it pause?

Post by armando_rod »

I'm not trying to say that this HVE TO BE THE WAY I WANTED.

I come here to give feedback man, this a forum.

That was my opinion as a long time user of another torrent app, I was using it for years, now I use qbt and not going back and never said it!

If you dont intend to change well okay, its not my project.

( the next time a user gives you feedback dont try to respond like "its my app and I do what I want to" wich is true but for a more engaging community you should try to explain why this way is the correct way to do it and maybe the user would agree with you. )
loki

Re: If pause is really stop, why call it pause?

Post by loki »

The reason being, if you're keeping torrents in your client for the explicit reason of knowing what you downloaded, and possibly when, then you will notice once you move or delete files from a torrent it shows different values than 100% I think the operation is more dynamic, and sledgehammer brings up a good point that it is probably more accurate, it actually shows current value based on data check.

The easiest way around it of course would be to remove the torrents you have no intention of using in future, especially if you already delete the data... why would you keep them in the client, just to take up space? (This coming from someone who has about 10 a week added, it would add up real quick if I didn't remove them from the list once I'm done with them or move them.)
ciaobaby

Re: If pause is really stop, why call it pause?

Post by ciaobaby »

I'm not trying to say that this HVE TO BE THE WAY I WANTED.

I come here to give feedback man, this a forum.
Maybe, ... but you are complaining about something that is YOUR OWN FAULT! It is NOT a qBT problem at all, you are expecting one torrent client to behave as badly as uTorrent and it's stable-mate BitTorrent do.
As far as I am aware those are the ONLY ones that will allow the user to remove the payload without giving a warning, and the reason is historical. The "payload check"  during pause/stop was disabled by default to reduce the running footprint. There was a toggle in advanced preferences to turn it back on at one time, (back when uTorrent could run more than ten jobs without falling over).
BitTorrent prior to version 6 also checked if the payload was still there, it is ONLY when BT inc dropped the open-source BT Protocol engine and switched to the uTorrent closed-source engine that it does not.
If I stop taking beer of the fridge well I cant be aware if there are beers or not.
Of course;

The possibility of the fridge being simultaneously full and empty (of beer) are both equally valid until the outcome is observed (paraphrasing Erwin  Schrödinger on quantum physics) (No domesticated felines were harmed in creating this hypothesis)
User avatar
Nemo
Administrator
Administrator
Posts: 1744
Joined: Sat Jul 24, 2010 6:24 pm

Re: If pause is really stop, why call it pause?

Post by Nemo »

[quote="armando_rod"]
I'm exiting the progrma via the [X] button on upper right.
[/quote]

You need to enable close to tasbar within the options, otherwise it will close the whole application instead minimizing and letting it run on the background. (If im right, at work at thr moment).

[quote="armando_rod"]
( the next time a user gives you feedback dont try to respond like "its my app and I do what I want to" wich is true but for a more engaging community you should try to explain why this [quote="armando_rod"]
( the next time a user gives you feedback dont try to respond like "its my app and I do what I want to" wich is true but for a more engaging community you should try to explain why this way is the correct way to do it and maybe the user would agree with you. )
[/quote][/quote]

If you did took your time to read the previous pages you would know your answer. Its perfectly correct how we explain it to you, no need to feel being attacked. Your opinion is always welcome, but there are certain things that definitly not going to be changed.

As sledge mentioned, uTorrent doesn't check for thr payload at start and thats why it shows 100% while it actually isn't. qBittorrent does check for the data and if it isn't there it shows 0% (very logical).

Im getting tired of this (pause button) discussion and may lock this topic. Next topic that gets opened with similiar subjects will be removed by me.
sledgehammer_999
Administrator
Administrator
Posts: 2443
Joined: Sun Jan 23, 2011 1:17 pm

Re: If pause is really stop, why call it pause?

Post by sledgehammer_999 »

[quote="armando_rod"]
I'm not trying to say that this HVE TO BE THE WAY I WANTED.

I come here to give feedback man, this a forum.

That was my opinion as a long time user of another torrent app, I was using it for years, now I use qbt and not going back and never said it!

If you dont intend to change well okay, its not my project.

( the next time a user gives you feedback dont try to respond like "its my app and I do what I want to" wich is true but for a more engaging community you should try to explain why this way is the correct way to do it and maybe the user would agree with you. )
[/quote]

Sorry for the late response. I didn't mean it that way. Thank you for the feedback.
I just explained why that functionality is the way it is.
arzine

Re: If pause is really stop, why call it pause?

Post by arzine »

Request: Add "Stop" feature?

On uTorrent, I normally just stop seeding the torrent a week after I'm done watching the series, I know it isn't something major but putting it on "Pause" is kinda unsightly. Also, when I move it into my archiving drive, it goes automatically to download.

So, this is what I suggest:
When "stopping" a seeding torrent, move it to a  "Complete", to which qBittorrent would not give a care in the world about what happens to that file(s)/torrent(s).
This would mean that "Seeding" (probably under "Downloading"?) would need to have a label on its own and "Queued Seeding" would remain in inactive. This just helps in sorting and visual, mostly because I can see what I'm seeding and what I'm downloading (and not care about stopped torrents), no doubt, colour-coded.
sledgehammer_999
Administrator
Administrator
Posts: 2443
Joined: Sun Jan 23, 2011 1:17 pm

Re: If pause is really stop, why call it pause?

Post by sledgehammer_999 »

to which qBittorrent would not give a care in the world about what happens to that file(s)/torrent(s).
Then those torrents don't belong in qbt in the first place. They should be removed.
bt clients aren't a "library" program.
Misapoes

Re: If pause is really stop, why call it pause?

Post by Misapoes »

Hello,

I've installed qbittorrent because of ninite, I'm a public tester for them to decide which programs should be on ninite's list. I'm happy with it except for the pause/stop thing, I find this annoying enough to change clients if what I want isn't possible. So my question:

Can you stop a torrent or not or will it ever be added? I like to stop seeding my torrents after some time and before I actually use the downloaded torrent. However, pausing it makes everything bright red like there's something wrong or incomplete and the status is paused instead of complete, so I have no way to quickly see if a torrent is actually paused and not yet done downloading or completed. I have no idea why the developers chose to make it bright red even when completed.. It's all very counter intuitive which seems the opposite of the only argument given for the decisions the developers made ("making it more simple by removing the stop button")

Quick note: I do not want to start a discussion, I simply want to know the answer to my question. Thanks!
sledgehammer_999
Administrator
Administrator
Posts: 2443
Joined: Sun Jan 23, 2011 1:17 pm

Re: If pause is really stop, why call it pause?

Post by sledgehammer_999 »

The pause button stops any transfer and drops all connections.
There is no "completed status". You can see which are completed by sorting by the "done" column. 100% torrents are completed.
About the colours: http://qbforums.shiki.hu/index.php/topi ... l#msg14715
Misapoes

Re: If pause is really stop, why call it pause?

Post by Misapoes »

[quote="sledgehammer_999"]
First of all qBittorrent isn't utorrent.
Secondly, when a torrent is stopped in utorrent and you delete manually the files, utorrent doesn't pick up the change. It doesn't care. The story is different with qBittorrent. It does check if the files are there even when paused. I don't intend to change that.
The difference is that utorrent continues to show 100% (which is false), but qBittorrent shows 0%(which is true). I think qBittorrent does the right thing here.
[/quote]

This is exactly what he was saying though, the average user wants enough control to at least decide that the client doesn't do any checks on files anymore, that no resources get used by the client.I think the beer analogy worked perfectly in this example. You are somewhat correct that putting this functionality in a pause function would be false (even though I'm of the opinion pause merits no checks until I unpause it, it should after all be paused in its functions) But that is why he, me, and a lot of other people would like a stop button, a complete stop without any checks. The download completed until 100% but the files aren't necessarily still 100%.

This also brings me to another point, the average user doesn't want to deal with clumsy relocating functions through a client, they want to be able to move it manually through for example windows explorer without that changing things in the client. (ie showing 0% suddenly)

Also, is there any chance that editing the color scheme will be included in the default upcoming releases?

Even though I like qbitorrent myself (even with the flaws) me and ninite's team are having a hard time deciding if qbittorrent will be staying, we're just getting too much confused user feedback over it. Developers should be taking these things in account, as modern design principles dictate, not just their ideals. Especially since the µtorrent fiasco will cause a lot of migration from average users.
Last edited by Misapoes on Sat Mar 07, 2015 10:26 pm, edited 1 time in total.
User avatar
Nemo
Administrator
Administrator
Posts: 1744
Joined: Sat Jul 24, 2010 6:24 pm

Re: If pause is really stop, why call it pause?

Post by Nemo »

This is exactly what he was saying though, the average user wants enough control to at least decide that the client doesn't do any checks on files anymore, that no resources get used by the client.I think the beer analogy worked perfectly in this example. You are somewhat correct that putting this functionality in a pause function would be false (even though I'm of the opinion pause merits no checks until I unpause it, it should after all be paused in its functions) But that is why he, me, and a lot of other people would like a stop button, a complete stop without any checks. The download completed until 100% but the files aren't necessarily still 100%.
Im not going to discuss this again. I still agree with ciao and sledge with this (see our old posts, my opinion hasn't changed). You can try the alpha out to see if something has changed maybe meanwhile.
Also, is there any chance that editing the color scheme will be included in the default upcoming releases?
There are plans as I have understood but no ETA.
Even though I like qbitorrent myself (even with the flaws)
Which program doesn't have flaws? There is always something. Its personal what every person likes or not; You can't please everyone. There are several things that are being worked on already. Go to Github and see the milestones for example. Outside that alot of ''under the hood'' changes are being made, see the alpha changelogs.
me and ninite's team are having a hard time deciding if qbittorrent will be staying, we're just getting too much confused user feedback over it.
If qBittorrent will be staying? Confused users? Im not even going to respond to this.
Last edited by Nemo on Sun Mar 08, 2015 12:03 am, edited 1 time in total.
Locked