View Single Post
Old 04-11-2011, 11:40 AM   #9
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,465
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
I agree that they shouldn't have precedence. What I am suggesting is that you warn the user and (possibly) clear the startup restriction.

The restriction differs from the sort tweak in that the startup restriction is in preferences, making it more likely that it will be changed.

What I am trying to avoid is bug reports/complaints saying something to the effect of "I set a restriction and it is being ignored." Such a report will be impossible to debug. If the view plugin hassles the user, then at least there is a chance that the user will figure out what is happening.

BTW: for the same reason you might also want to hassle the user if a startup sort list is set that is different from the one in the view. I am less worried about this one, though, because tweaks are a bit harder to find and set.
chaley is offline   Reply With Quote