View Single Post
Old 07-06-2019, 10:37 AM   #16
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,708
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
For the purposes of this discussion, I really think we should separate #1from #2 & #3. In other words: "how do we want to treat #2 & #3?" And then "how do want to treat #1?"

Lumping them together only creates confusion, I think. Especially in light of the fact that I think #1 is a no-brainer: make it a manual menu option (so people can validate without having to save first), AND automate it upon Save(As), if feasible (because having manifest properties properly set is not an optional part of the spec, and properly setting them will never cause problems).

That leaves #2 and #3. Which I think should be combined into one, backward-compatibility action, and should be optional. Whether it's optional because it's left as a manual menu-action only, or because the user can opt out of automatically having them happen upon Save(As) makes no difference to me.

Last edited by DiapDealer; 07-06-2019 at 12:25 PM.
DiapDealer is online now   Reply With Quote