diff options
author | Tor Lillqvist <tlillqvist@suse.com> | 2013-05-07 17:54:46 +0300 |
---|---|---|
committer | Tor Lillqvist <tlillqvist@suse.com> | 2013-05-07 18:07:02 +0300 |
commit | dcf11ef35fbd0012c1603b53704fa05afdb2ce7f (patch) | |
tree | 82dcfe0a3af4fff30bc8ed4336fa19e87f3e86be /vcl | |
parent | 58fc0b1a14e827ab0b9ee4da8630c1e3ee10a19c (diff) |
Different fix for bnc#777788
Use the same GUID in the file dialog for the FILESAVE_AUTOEXTENSION
case as for the FILESAVE_AUTOEXTENSION_EXTENSION case. The former is
used when exporting to PDF. Exactly why using one GUID for the dialog
causes it to use the default folder as set by SetFolder(), and the
other not, I have no idea. Are the GUIDs we use arbitrary (and unique
to the OOo/LO codebase), or does either of them, or both, have some
magic meaning to Windows?
FILESAVE_AUTOEXTENSION is also used in other cases than exporting to
PDF. It remains to be seen whether this change will cause noticeable
behaviour change interpreted as a harmful regression. Or whether the
change of default folder for PDF export will do that, for that matter.
Diffstat (limited to 'vcl')
0 files changed, 0 insertions, 0 deletions