I'm on the fence over that one. I've made the whole "remember and apply last view" behaviour an optional thing. I think it could get a little more confusing if I allowed Calibre to override it in some cases. For instance I don't let the Calibre "sort columns at startup" tweak override sorting. So for consistency I don't think startup restrictions should have precedence either? If a user is into both using restrictions and using views, I consider it "highly likely" that they will configure the restriction into the view, in which case there is no conflict anyways.
It's a good point though that I will mention in the front page of the plugin to explain that behaviour.
|