6.32 bug in deleting single files

[oferlaor]

Say I have a file that is comprised of 10 different parts.

If i try to delete a particular part from the download list, it will delete the rest of the parts from there too.

This used to work fine. Looks like a bug.

[itimpi]

This is expected behaviour if you queued the file as a set. If you want to be able to delete individual files you have to open the set before queueing it, and then add the individual files from there.

[oferlaor]

Say I have an NZB containing a file set.

However, I want to change priorities. I want RAR part 12 to be the first one grabbed. I want to remove RAR part 11 and I want RAR part 5 to bypass filters.

This used to be possible, but is no longer possible...

The reason I ask is that a RAR set had a problem and I found that I needed to download it again. More specifically, I needed about 6 files from that set to enable the PAR2 to fix it. In the past, I used to be able to minimize the downloading by sorting, bypassing filters or simply removing the unnecessary files from the list. None of these options no longer work, which means I have to download the entire RAR file set for no apparent reason...

[itimpi]

It is if you start by loading the NZB into a Post list, open up any file sets that have been compacted and then queue the files individually. This has always been the behaviour with v6.

Quade has been talking about the possibility of breaking files out of compacted sets after they are queued for download so they are easy to manipulate for those who want to fine-tune their downloads, but so far this has not happened.

[Quade]

The reason I ask is that a RAR set had a problem and I found that I needed to download it again. More specifically, I needed about 6 files from that set to enable the PAR2 to fix it. In the past, I used to be able to minimize the downloading by sorting, bypassing filters or simply removing the unnecessary files from the list. None of these options no longer work, which means I have to download the entire RAR file set for no apparent reason...

If you simply add the whole thing, download it to the folder with the existing rars, it'll just download the ones that are missing. You'll want to delete the bad ones from disk first (if any). With a valid par, Newsbin checks the files on disk and won't re-download RARS that are already in the folder. It downloads the first chunk then confirms that the existing file is the one it's looking for. This works if autopar is enabled.

It's equally valid to just add the 6 rars directly by loading the NZB into a lost list (as D suggested) using the "Load NZB" button on the toolbar.

[oferlaor]

To be honest, I am not really sure I understand why this change was made.

The old way (selecting specific file parts and changing priorities or removing them completely) seems much more logical.

If I can't change anything on a file part, why even bother letting me select it?

[Quade]

You can do anything in 6 you could do in 5. In addition though you can add complete sets to the download list and reasonably expect most of them to assemble and repair on their own. I mean, if you want to add the rars as individual files, you can. Normally it's better to add them as sets so, the PARS are joined with the rars.

It's not clear to me why you can't just do what I suggested to complete your download.

[oferlaor]

Well, I downloaded it to the same directory and for some reason it simply kicked out the entire set as a duplicate. so, in the end, I had to mark the entire thing as "bypass filters" and download the whole thing.

Obviously, this is not a typical case, rather I'm pointing to an incorrect UI behavior, IMO.

It just looks to me that this is the intuitive behavior:
1. When you select one or more file and delete it, it should delete (or prioritize, or bypass filter) on the item I just selected (not the file set).
2. When you select the entire set and delete (or prioritize, or bypass the filter), THEN it should do the same for the entire set.

functionally, this simply seems like incorrect behavior. If I can't do anything on a particular file (only on a file set), then i shouldn't be able to select it and right click it - only the entire file set...

[DThor]

In the end, you want the post. Even a single rar file is a conceptualization of many individual posts to usenet, but there's no complaints about not being able to manipulate on that level by anyone. I think it's just progression, and might take a little getting used to by people used to the more micro-managed approach. The most important thing is when there's some sort of problem getting the post, do you have an easy to use method to finish it off? Sure, there might be the occasional example that's a slight struggle, but the system that's there now works, hands off, for the vast majority of posts. When it doesn't, there's a solid system in place to deal with it, but yup, it's not identical to the way you might do this in the older version. I really think it just needs getting used to, and the one line as a single post saves you so much, I think it's better behaviour overall.

DT

[oferlaor]

It's not intuitive to me...

It is kind of like selecting a single file in a directory and deleting it and the operating system deletes the entire directory...

Why let me select a single file when I cannot do anything to it anymore...