Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | "Background setting for all pages?" does not work properly | ||
---|---|---|---|
Product: | Impress | Reporter: | rogerwesson <oo> |
Component: | formatting | Assignee: | groucho266 |
Status: | CLOSED DUPLICATE | QA Contact: | issues@graphics <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | OOo 2.4.1 | ||
Target Milestone: | --- | ||
Hardware: | Unknown | ||
OS: | Linux, all | ||
URL: | http://www.star.ucl.ac.uk/~rwesson/wolas.odp | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
rogerwesson
2008-12-04 19:06:38 UTC
Reproducible. Also happens in 3.o final. Reassigned. This is not really a bug, at least not in Impress. Changing the background for all slides works only when the background of the (one) master page is used by all slides. In the bug doc, however, most, if not all, slides have set individual backgrounds. These backgrounds all map to the same bitmap and the user easily gets the impression that changing one background should result in a change to all other backgrounds that show the same bitmap. If every slide would show a different bitmap it would become clearer: the master page background is obscured. Changing it as described above does not have any effect. The only way to fix this is to modify the document. Reset the backgrounds of all slides to None and set only the master page to the desired background bitmap. Is this really not a bug? Whether I am choosing a bitmap, or a fill colour, or a gradient, or whatever, then answering yes to "Background setting for all pages?" does not apply the background setting to all pages. This seems like undesirable behaviour, and is very counterintuitive. If individually editing each slide is really the only way to have a single background throughout this presentation, then that's really very inconvenient. Since the bugdoc is no longer abailable I can only guess that the document had multiple master slides. In this case this issue is fixed with issue 109210 *** This issue has been marked as a duplicate of 109210 *** closing dupe |