inherited from OOo. affects any LibO release. the "Tools/Extension manager" menu item cannot be assigned to any keyboard shortcut or toolbar button. if you select "Tools/Customize/Keyboard" or "Tools/Customize/Toolbars/Add" you will find that Extension Manager never appears in any of the available command lists.
Thank you for reporting this bug. I also can't find it. It would be a improvement to have.
I'd like to hear impressions from a developer... could it be an easy hack?
"extension manager" not yet available as a custom menu item. tested on 4.1.1.2 and 4.2.0 master Sept.10.
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Checking the menu xml, Extensions Manager doesnt have an uno command and instead is "service:com.sun.star.deployment.ui.PackageManagerDialog". @Maxim: is there a means of setting a shortcut to such an entry and having it accessible in the customization dialog?
(In reply to Jay Philips from comment #5) > Checking the menu xml, Extensions Manager doesnt have an uno command and > instead is "service:com.sun.star.deployment.ui.PackageManagerDialog". > > @Maxim: is there a means of setting a shortcut to such an entry and having > it accessible in the customization dialog? Currently I'm not aware of any way to add this to the customization dialog. This "service:" thing is not a name of an internal command, but just a URL of a service. As a workaround it's possible to manually edit the toolbar or accelerators xml. Another option is to create a macro that executes this URL, and add a button to this macro to the toolbar.
a macro could be then converted as an extension... and extension can be bundled with LibO IMHO the extension manager deserves to be a standard toolbar button.
(In reply to Maxim Monastirsky from comment #6) > Currently I'm not aware of any way to add this to the customization dialog. Well, I meant in its current state. Of course we can create a new command that will internally call this service, and use that new command for the menu, instead of directly referencing the service.
(In reply to Maxim Monastirsky from comment #8) > Well, I meant in its current state. Of course we can create a new command > that will internally call this service, and use that new command for the > menu, instead of directly referencing the service. I would believe that would be the easiest solution if it is possible and simple.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.