newsbin.com

I'm a long-time Newsbin user, and finally upgraded to v6 only in the hope that the autopar was going to work faster. Now that I've (finally!) re-arranged the panels how they should be, I have one huge irritating thing left to fix that I cannot seem to turn off that's a complete deal-breaker for me.

How exactly do I completely disable the "Compact View" so that whenever I open a NZB file I don't have to click on the + to un-collapse to see the individual files in each group of files?

Thanks in advance!

You cannot. That view is built into the architecture of v6.

Thanks for the quick answer! Unfortunately until this is user-selectable v6 is going to be pretty useless to me, I cannot fathom why it is not. After some googling I see this has been requested for a couple of years.

If I go back to v5 do you happen to know if I can still somehow retain my configuration, or is there a specific downgrade install procedure published somewhere? Retaining any spools or headers does not really matter to me otherwise.

The configuration file should be compatible. You might have to adjust the download pathing when you switch back to 5.59.

I might be able to make it compact or not compact. You'd have to re-download headers or accept that old headers are compacted and new not. You won't be able to switch back and forth. It'll either be compacted or not compacted. You'd have to accept significantly longer load times and much larger data files too. The whole point of compaction is that it reduces the DB3 file sizes by probably a factor of 3-10 (meaning a compacted 30 GB DB3 file will be 3-10 times bigger uncompacted). It'll probably break AutoPAR too.

I was going to say it will never happen but, I suppose a hidden option nobody could enable by accident could be possible.

Thanks for the downgrade tip.

I presently do not have any headers at all to worry about . I stopped maintaining any tangible backlog in Newsbin a few years ago, so I won't have any big files to manage going forward, less than 1GB probably at the very most.

The thing that would affect me would be the loss of autoPAR. The sole reason for upgrading to v6 was to (hopefully) obtain better autopar performance which if I am not mistaken is now comparable with threaded par2cmdline?

Repair is multi-core in 6.XX.