Bug 145520 - LODraw: Export dialog forgets last used format
Summary: LODraw: Export dialog forgets last used format
Status: RESOLVED DUPLICATE of bug 54035
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-03 05:53 UTC by James Harkins
Modified: 2021-12-13 17:32 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 James Harkins 2021-11-03 05:53:54 UTC
Description:
After exporting a drawing once to a specific format, exporting the same drawing again defaults to JPEG format (no matter what format had been chosen before).

Steps to Reproduce:
1. Create a drawing.
2. Export to, say, SVG.
3. Change something in the drawing and export again. The format selector has flipped back to JPEG.

Actual Results:
The user's previously selected format has been forgotten, and the dialog reverts to the default.

Expected Results:
The dialog should remember the user's previous format selection.


Reproducible: Always


User Profile Reset: No



Additional Info:
If a user has exported a particular drawing to a specific format once, it's reasonable to suppose that the export format chosen is the desired final result.

It's a quite common workflow to edit, export, verify the result, fix problems, and export again, for an unknown number of cycles. Requiring the user to reselect the format every time is unnecessary mental static.
Comment 1 onlyshilps 2021-12-02 07:01:30 UTC
Not reproducible using:

Version: 7.4.0.0.alpha0+ (x86) / LibreOffice Community
Build ID: 4ac9032163cf55c160145373e7c41741c9c339ca
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 2 Buovjaga 2021-12-13 17:32:51 UTC
I repro and there is an older request

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