[Libreoffice-bugs] [Bug 112237] Cannot get description of used commands in new customize dialog
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Tue May 21 12:17:16 UTC 2019
https://bugs.documentfoundation.org/show_bug.cgi?id=112237
--- Comment #16 from Muhammet Kara <muhammet.kara at collabora.com> ---
(In reply to Regina Henschel from comment #15)
> The problem for me is not the missing description for the list on the left
> side, but the missing information for the already inserted commands on the
> right side.
>
> Example: The 'standard' toolbar in Writer has two commands 'Symbol' with
> exact same icon. You cannot determine in the Customize dialog what each of
> them does. You have to enable both and leave the dialog. Then you can
> examine them. (As long as you customize a toolbar, no chance if you
> customize a menu. But that is another bug.) One is 'uno:InsertSymbol' the
> other is 'uno:CharmapControl'. It would be good to have this information
> already inside the Customize dialog.
>
> Heikos suggestion, to show a tooltip with uno command, would solve the
> problem at least for advanced users, but conflicts with the tooltips of the
> dialog itself. A one-line field with uno command below the right list would
> be good. Or a line with the affected uno command in the Modify drop-down
> list.
Okay. Hear this please:
* A pair of radio buttons above (near?) the description box to determine which
side's description will be shown.
* A checkbox above/near the description box to make uno commands visible inside
the description box. (Maybe saying 'Show uno command')
How does that sound?
If good, then we will need a design proposal to fit those radio buttons and the
check box into the dialog without ruining it.
Btw, the pair of radio buttons might be also replaced by a checkbox since it is
a binary choice.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190521/3eb8f6fe/attachment.html>
More information about the Libreoffice-bugs
mailing list