by tazmeister » Sun May 01, 2011 7:51 pm
I've seen this in B8 B9 and B11
I'm about to switch to B12
The thing is autopar has never been good about keeping a clean list of it's progress
it's just not been a problem because the messed up list was always in a separate tab.
Now I can't ignore all the entries it leaves around
Sometimes it just doesn't finish repairing
Sometimes I'm not sure what it's status really is, but If I run quickpar some of those times everything is there and intact so it looks like autopar just didn't update the fact that it was done
sometimes I can run quickpar and it autopar hasn't repaired the files and it hasn't downloaded any of the extra pars it knows about
and so on
I've been using this app for years, and autopar has always been unreliable
but like I pointed out above it didn't matter too much because the spam it left didn't obscure the download list
When it worked I was happy, when it didn't work though it didn't bother me mostly because there are actually a huge number of possible cases it actually has to handle if it is expected to work all the time. At least when it didn't complete or something, I knew that the app at least had finished downloading everything it thought it needed, so I could then finish the repair by hand
I think 5.59 (maybe just the betas) newbin wasn't actually storing a list of extra pars. This sucked because I had to search for the posts to find the pars again
this has been fixed, though I don't like having those extras in the download list since it still breaks the old paradigm that items in the DL list are items it will definitely still be downloading
Basically, there are times where autopar just doesn't start checking even if a par2 file was downloaded
sometimes though NB didn't download the first par2 even though it was selected so autopar didn't start
then sometimes autopar just stopped partway though the repair or the check for no apparent reason
sometimes it incorrectly thought something was broken so it would download all the extra pars
sometimes it would correctly notice a problem but would never start downloading the pars
and so
I think I've seen just about every combination of final state plus correct or incorrect response to that state occur
I just figured that it was understood that autopar could never get things right 100% of time since there are so many minor ways someone can mess with how they create their pars, and each of this ways potentially requires a complete set of code to check for that state and handle it
Overall autopar works the majority of the time in the sense that it does fix the files and unarchives things if needed, on the other hand I'd guess that it correctly updated the UI after the fact less than half the time
For me, as long as it didn't mess things up and didn't force me to look at the >50% incorrect list of autopar statuses I was fine with it
But by removing the autopar tab and moving that inaccurate list of to the DL list, it's impossible to ignore the issue and it screws up trying to check on the status of the download
NOTE: the download is a definitely a separate thing from the check/repair/extraction process
It's fine to have some sort of list that covers the end to end workflow, but I really rely on having a distinct display of the state of just the download phase
mostly because the app doesn't get the subsequent parts right reliably and I doubt anyone will ever write an app that manages that just because of the huge range of possible ways someone can post a set of files plus pars