Bug 146268 - FILESAVE - Exporting a page as a .png image includes layers which are currently set to be both not visible and not printable
Summary: FILESAVE - Exporting a page as a .png image includes layers which are current...
Status: RESOLVED DUPLICATE of bug 53864
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-16 15:32 UTC by Martin
Modified: 2021-12-17 00:54 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2021-12-16 15:32:43 UTC
Description:
I created a file with several pages. On one of the pages, I created several layers on which to draw boxes for highlighting various different regions of the image. After drawing on those layers, I turn visibility and printability off for all of them to export my first "base" figure. The exported file draws all contents of all layers regardless of whether they are turned to visible or printable. I consider this unexpected behavior, as it severely limits the usefulness of layers.

Steps to Reproduce:
1. Create a Draw file.
2. Create a new layer and draw something on it.
3. Turn layer visibility and printability off.
4. Export image as a .png

Actual Results:
The exported .png file shows all contents of all layers, including those set to be invisible and/or not-printable.

Expected Results:
I would expect invisible and/or non-printable layers to not show up in the exported .png file.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.4.7.2
Build ID: 1:6.4.7-0ubuntu0.20.04.2
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Regina Henschel 2021-12-17 00:54:15 UTC
Yes, that is an old, still unsolved problem.

*** This bug has been marked as a duplicate of bug 53864 ***