Page 1 of 1

Processing option reset when Category changed

Posted: September 30th, 2014, 12:26 am
by DngrMs
Windows 8.1u1
Sabnzbd 0.7.18

Whenever I change the 'Category' of a download the 'Processing' setting is reset to the default. If I change the 'Category' before I change the 'Processing' option then all is fine.

This is reliably repeatable on my system (i.e. every time), do other people have the same experience?

Let me know if any configuration details would be helpful.

Great app, thank you.

Regards.

Re: Processing option reset when Category changed

Posted: September 30th, 2014, 4:02 pm
by shypike
It works as intended, but maybe not as you expected.

Re: Processing option reset when Category changed

Posted: September 30th, 2014, 7:34 pm
by DngrMs
Okay thanks although IMHO 'Category' has no apparent logical relationship to 'Post Processing' therefore a manual setting shouldn't be undone. Having said this it's not something I'm going to lose sleep over!

Re: Processing option reset when Category changed

Posted: October 1st, 2014, 3:42 am
by shypike
The Config->Category page allows you to setup attributes per category.
So the idea was that when you manually set the category, the attributes change accordingly.
Of course the argument can go the other way too, but that's how we looked at it.

Re: Processing option reset when Category changed

Posted: October 1st, 2014, 6:15 am
by DngrMs
shypike wrote:The Config->Category page allows you to setup attributes per category.
So the idea was that when you manually set the category, the attributes change accordingly.
Of course the argument can go the other way too, but that's how we looked at it.
Ahh... I hadn't looked at it this way, interesting. My post-processing is standard for all categories unless I choose to alter it, I wonder if I'm the exception or the rule?

It would be lovely, but perhaps difficult to implement, if 'post-processing' followed 'category' unless it was previously manually set.

Re: Processing option reset when Category changed

Posted: October 1st, 2014, 11:53 am
by shypike
That wouldn't be very difficult, but we like to limit breaking changes to main releases.
So 0.8.0 would be the first.
Noted.