Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 06/28/2013 07:05 AM, Kohei Yoshida wrote:
On 06/28/2013 08:34 AM, Markus Mohrhard wrote:

Actually these are normally not trivial as they have code indirectly
attached to them so you should first check that also the attached
actions have the same behavior or are surely unused. Normally the
string is mapped to a command id which is then used in the code. For
example the .uno:RenameTable can't be deleted because it has a lot of
code attached that is necessary. I could not find anything for the
.uno:Name command but if you say that it appears in the menu when you
delete the string definition there appears to be somewhere a hidden
mapping.

.uno:Name is mapped internally to FID_TAB_RENAME which is still very much used.

The way to find out the mapping from an .uno:Foo name to an internal event ID is to look into these .sdi files in sc/sdi/ (without the ".uno:" prefix). In this case there is this entry

SfxVoidItem RenameTable FID_TAB_MENU_RENAME
(SfxStringItem Name FID_TAB_RENAME)
[
...
]

BTW, I'm not 100% sure how these two are related - the one at the top and the one in the parenthesis. I'm not an expert on this sdi file syntax.

Anyway, even this small hint will hopefully be helpful.


Go figure that another one that seems so easy is not easy :-/ So, given that it's used internally - how do we hide it from the list so there isn't a duplicate.


Best Wishes,
Joel


Context


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.