View Single Post
Old 07-06-2019, 06:47 AM   #12
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I don't see any point in allowing a user to decide to NOT update the manifest properties when saving. Having the manifest properties correctly set is not a question of optional backward compatibility like the other two actions. It's a question of error/not error when validating. So while I think it's fine (and wise, in fact) to continue to allow a user to manually update the manifest properties anytime they like (via a menu action), I see no point in allowing them to opt out of an automatic update of the manifest properties when saving.

As for the other two actions: I have no preference as to whether or not they're manual menu actions, or if they're applied automatically at save time, or both (though I'd suggest both menu actions be combined into a single "ensure backward compatibility" action). I'd just rather a user not have the backward compatibility actions forced upon them. Whether that's achieved by NOT automatically doing it when saving, or by offering a preference to opt out of automatically doing it when saving makes no difference to me.

Last edited by DiapDealer; 07-06-2019 at 07:05 AM.
DiapDealer is offline   Reply With Quote