Created attachment 186780 [details] Master View compared LO MSO Master Slide deck in Sibebar should have more options. Comparing with MSO, checkboxes for Title, Footers would be first. Setting Background would be handy. Also, just LO issue, not clear why "Master Slide" dropdown is empty here, should not be.
Reason here is not only that MSO has more useful options, but especially those like Title and Footers (containing slide number etc) can be defined in the document but not shown. Easiest way to show them is with those checkboxes.
Under Slide > Master Elements... you find the checkboxes. Sufficient for its purpose, IMO. Do you agree? The "Master Slide" dropdown is empty since you have access to it via the slide pane. In normal mode you can pick one of the master slides here and apply it to the current slide. We could hide the disabled controls. Is it needed?
(In reply to Heiko Tietze from comment #2) > Under Slide > Master Elements... you find the checkboxes. Sufficient for its > purpose, IMO. Do you agree? I didn't know about this. Why would it be on diff. places... My classical workflow is to use Master View. So my opinion is: no, not sufficient. Can those Master Elements be added under current Master Slide deck content? > The "Master Slide" dropdown is empty since you have access to it via the > slide pane. In normal mode you can pick one of the master slides here and > apply it to the current slide. We could hide the disabled controls. Is it > needed? I think it is needed for someone to be sure in which Master Slide is. I see no reason not to be shown.
(In reply to Timur from comment #3) > My classical workflow is to use Master View. So my opinion is: no, not sufficient. > Can those Master Elements be added under current Master Slide deck content? Cannot follow. You expect two out of many other options at the properties tab / Master Slide deck to... well, switch it on/off once per presentation and accept it to occupy a lot of space. > I think it is needed for someone to be sure in which Master Slide is. I see > no reason not to be shown. More opinions please.
(In reply to Heiko Tietze from comment #4) > More opinions please. Here's an opinion... 1. "Master Elements" does nothing for me: I can click things on or off - that doesn't make them appear in the slide. That's in a blank slide deck, not when opening a specific template. I don't see footers or a page number. 2. The distinction between "Master Elements" and "Master Objects" is not clear enough. After all, the "Master Elements" are (Drawing) Objects on the master slide. 3. If I can toggle "Master Elements" from the Slide menu, why not also from the Slide properties section of the sidebar? 4. Why is "Master Elements" a dialog rather than a submenu of the Slide menu, seeing how it has four fixed items and no sub-panes etc.?
Topic was on the agenda at the design meeting but did not receive further input. Master Elements... allows to disable the footer (and header for Notes). That's sufficient and we don't need to show the controls on the primary UI. => WF (In reply to Eyal Rozenberg from comment #5) > 1. "Master Elements" does nothing for me It shows/hides elements on master. Try with a shape on the master, switch the option off in the normal view, and go to another slide. We have an issue with the update mechanism here, which is likely reported somewhere else. And OT here. > 2. The distinction between "Master Elements" and "Master Objects" is not > clear enough. RTFM? And OT here, the request is, more or less, to show the Master Element options on the main UI. > 3. If I can toggle "Master Elements" from the Slide menu, why not also from > the Slide properties section of the sidebar? Access to Master Elements from the sidebar, why? Rhetorical question, IMO the sidebar should offer quick access to frequently used options, without replicating every attribute from the dialogs. > 4. Why is "Master Elements" a dialog rather than a submenu of the Slide > menu, seeing how it has four fixed items and no sub-panes etc.? Don't see an advantage to have ME in a submenu. It has the drawback to bloat the API as every single checkbox needs an UNO command.