only through using it can we make a menu more intuitive :)
a few MINOR suggestions:
when we right click on a template (at MANAGE TEMPLATES), it will bring up
SET AS DEFAULT
I think, the separator should go below "set as default",
cause the first two menu items refer to the IMMEDIATE use of the template,
while the other 3 refer to ORGANIZING the templates...
- - -
the main suggestion that I'd like to propose, however, is
OPEN to "Open new document"
EDIT to "Edit this template"
personally, I was in love with the briefness of this menu...
but making it clear(er) what menu items are for should enjoy priority :)
- - - thank you for developing LibreOffice - - -
Steps to Reproduce:
1. File / Templates / Manage Templates right click on a template
since the context menu that comes up is like this:
the user who wants to OPEN the template, both to see what's inside (styles) and to perhaps edit it..
will be frustrated cause a new document is created...
which means, the template couldn't be accessed :)
as it couldn't be opened :)
there is another reason why this additional information "new document" in addition to "Open" should be added, namely, that
the user can land here, at Manage Templates from File / New / Templates...
in which case she or he will want to "create a new document"...
but if s/he right clicks before just clicking on the template blindly,
s/he will see "Open" and "Edit" as two options...
neither of which would be what she expects...
cause what the user wants in this case is "create a new document" and not "open" (a template)
when going CTRL+SHIFT+N (or file/templates, manage templates),
the it should be clear for the user
that the options are OPENing a new document
and editing the template
OPENing (the template that has been right-clicked)
EDITing (the template that has been right-clicked)
User Profile Reset: No
I agree to both suggestions
a) separator below "set as default"
b) "Open new document". Perhaps also "Use" and "Edit" would make it more clear
Good point, let's continue in the other ticket.
*** This bug has been marked as a duplicate of bug 104074 ***