https://bugs.documentfoundation.org/show_bug.cgi?id=127421
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |libreoffice-ux-advise@lists
| |.freedesktop.org,
| |vstuart.foote@utsa.edu
Keywords| |needsUXEval
--- Comment #1 from V Stuart Foote <vstuart.foote@utsa.edu> ---
The DirectTo commands were added to toolbars and the MUFFIN Notebook Bar
specifically to by-pass their export dialog(s).
.uno:ExportDirectToPDF
.uno:ExportDirectlyToEPUB
commands provided as alternatives to the
.uno:ExportToPDF
.uno:ExportToEPUB
commands which will always launch the dialog.
We already can customize the toolbars, menus, context menus, and even assign
short-cuts to any of themn (via Tools -> Customize).
Also, the DirectTo commands pick up the Export dialog's configuration as
recorded to user profile--and so are statefull allowing you to set your export
preferences, e.g. Compression Tagging, or the use of the Hybrid PDF (which
appends the ODF archive into the PDF).
Do your first export using the dialog, subsequent will pick up any changes from
defaults from your profile.
Given that, prefer to keep the button actions linked to the DirectTo commands.
IMHO => WF
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 127421] Export as PDF/EPUB by default on Tabbed bar instead of Export directly as PDF/EPUB · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.