https://bugs.documentfoundation.org/show_bug.cgi?id=151918
--- Comment #16 from Mike Kaganski <[email protected]> --- (In reply to Eyal Rozenberg from comment #15) > > and wherever it gets finally landed, it may get a "make default" > > button, to allow *also* to store this piece of settings into the > > profile as a default value for newly created documents. > > I'm not against this in principle, but: > > * If you did this everywhere it is possible, you would need to allow every > feature of, say, the default page style and default paragraph style to be > "made default". That's a lot of buttons... > * You may also/instead want to consider the 'mirror' approach to your > suggestion, i.e. having the LO options dialog have buttons for "adopt > settings in current document as the default for new documents". > * Wouldn't some of these "default value" settings actually belong in the > template file rather than the app option? Every default may (and best does) apply to templates. But yet: 1. There are these existing controls in Options, that allow to set the non-template defaults; and if they are needed at all, we should decide where they are; 2. There are cases where even templates don't suffice - like Calc column default width/height, something hardcoded, and used e.g. when you delete some rows/columns, and Calc appends the new stuff, and there are people who consider impossibility to customize it to be a bad thing; 3. It is good to not multiply places where you configure one thing. E.g., when you think about font, you go to Format->Character; and having font settings *also* in other place (in Options just for defaults) is a bad UX; 4. Having a single "apply this document settings as global defaults" would be inconvenient, given how many things may come from the document, which user is even unaware of (does user know e.g. if the printer setting would be stored, and then cause delays when the network printer is turned off?). -- You are receiving this mail because: You are the assignee for the bug.
