| Summary: | Draw: PNG export options not remembered | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | crxssi |
| Component: | Draw | Assignee: | Julien Nabet <serval2412> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | barta, heiko.tietze, jmadero.dev |
| Priority: | medium | ||
| Version: | 4.1.0.4 release | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=39204 https://bugs.freedesktop.org/show_bug.cgi?id=56899 https://bugs.documentfoundation.org/show_bug.cgi?id=89192 |
||
| Whiteboard: | target:7.1.0 target:7.0.0.2 | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 100467 | ||
|
Description
crxssi
2013-07-30 21:15:39 UTC
I can confirm this problem in Draw on Ubuntu GNU/Linux version 13.04 in version 4.1.04 of LO. There is currently no way to produce a reasonable sized PNG file from Draw. Additional info: It seems to automatically select a transparent PNG (good) but only saves it at a low resolution. I confirm it on 4.1.0.4 and 4.1.1.2 under Win7 64bit the "save transparency" flag status is not remembered. "interlaced" status is instead remembered the "save transparency" option was introduced in 4.1.x since I do not see it in 4.0.x releases. (In reply to comment #2) > Additional info: It seems to automatically select a transparent PNG (good) > but only saves it at a low resolution. I will point out that it is not "good" that it automatically selects the transparent option every time. It should remember the previous selection of the user. There are times you want it to be non-transparent and if you have to export several things, having to turn it off each time is annoying. If it remembers "mode" it should remember "transparency". I believe it is a good default to have it selected "on" the first time ever used, however. ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18 (In reply to QA Administrators from comment #5) > *Test to see if the bug is still present on a currently supported version > of LibreOffice (4.4.1 or later) I just tested this issue under LibreOffice 4.4.2 under Linux and it is still present. Interlaced setting is remembered and "Save Transparency" is not being remembered. (It is also not remembering the export format, but that is a different bug report). It is not inherited from OpenOffice, because OpenOffice had no "Save Transparency" option in PNG. Don't see this as an enhancement but an ordinary bug. User settings should be saved as it is the fact for Interlaced. No further input from UX needed. I gave a try with: https://gerrit.libreoffice.org/c/core/+/98485 Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b54f7fd93cc300fedac2f1b007dfc4e6a704b515 tdf#67560: PNG export option Save transparency not remembered It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-7-0": https://git.libreoffice.org/core/commit/bba303dd74f88fc1720b3ae000f5fa0fd54ded84 tdf#67560: PNG export option Save transparency not remembered It will be available in 7.0.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. |