| Summary: | Draw: no command to apply a master to all (selected) pages | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Mike Kaganski <mikekaganski> |
| Component: | Draw | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | buzea.bogdan, heiko.tietze, rb.henschel |
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 113354 | ||
|
Description
Mike Kaganski
2019-12-31 10:56:33 UTC
The same is also true for Impress where every slide can have a different master, which is a feature not a bug. "Apply to all pages/slides" might be needed but it doesn't fit into (single) slide design or (individual) page layout. How about a solution per macro? (In reply to Heiko Tietze from comment #1) > The same is also true for Impress where every slide can have a different > master, which is a feature not a bug. "Apply to all pages/slides" might be > needed but it doesn't fit into (single) slide design or (individual) page > layout. Impress and Draw might share much of the code - but they are not the same. So if something doesn't fit Impress, doesn't mean it should be excluded from Draw. And the UNO command might work uniformly, while not be present in the menus. Additionally, narrowing down the problem to "all" when it was spelled "all (selected)", where "selected" fits fine to Impress, is cheating ;-D > How about a solution per macro? Why not? Macros use UNO; effectively any macro is a sketch for a following implementation in C++. It might be a problem with the page pane. "Duplicate" does not work on selected pages too. In Impress you can e.g. select three slides and then use "Duplicate" and you get three new slides. In Draw doing the same you get only one new slide. So perhaps a bug with the page pane. (In reply to Mike Kaganski from comment #2) > > How about a solution per macro? > > Why not? Macros use UNO; effectively any macro is a sketch for a following > implementation in C++. I would close the request as WFM in that case. Or change component to extensions. (In reply to Heiko Tietze from comment #4) > I would close the request as WFM in that case. Or change component to > extensions. Ah no, I misunderstood you in that case: this is the issue that must be fixed, it's just the method of fixing that may be different... |