[Libreoffice-ux-advise] [Bug 155921] Macro menu for renaming, exporting, and organizing macros is very bad structured

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=155921

Heiko Tietze <heiko.tietze at documentfoundation.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |127591
                 CC|                            |libreoffice-ux-advise at lists
                   |                            |.freedesktop.org

--- Comment #1 from Heiko Tietze <heiko.tietze at documentfoundation.org> ---
(In reply to elias estatistics from comment #0)
> it go to edit menu for macros.
You mean Tools > Macro, or what is the "edit menu"? The summary is also "menu
... is very bad structured".

> I cannot move macros as plug & Play
In the object catalog of the macro edit dialog you want to drag 'n drop nodes
(eg. Access2Base > _License) to another macro. This would be usually a move
operation unless some modifier key is pressed. But anyway, making the object
catalog tree more interactive (copy, past, edit, delete, rename...) sounds
reasonable.

> I cannot rename macros by double click on its name
Double-click is typically Open, I would either try F2 or right click. But yes,
such a function is desirable.

> I cannot find 1 hour now how to rename, move, export macros to new
> libreoffice.
In the IDE module try Tools > Organize Macros > Basic: Oranizer.

> Why it is not plug and play and we need 2-3 menus for simple tasks?
Our hidden agenda is to promote R, of course. :-)

Seriously, the macro editor is not a primary function of an office suite and
obviously not so many users have the same workflow like you. Otherwise bug
reports would have been written... could be bug 120658.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=127591
[Bug 127591] [META] User Interface (UI) related Macro bugs
-- 
You are receiving this mail because:
You are on the CC list for the bug.