Why is a custom menu item greyed out?

I've been trying to add a custom menu to a document. I go through the motions
of adding the menu and saving it within the document, but when I click on
it, or any other menu on the menubar, it is greyed out. Assigning the menu
item to a macro action has no effect on this.

Also, if I put in sub-menu items the main menu stays black, but the submenu
items are greyed out.

I'm using LO 5.2.3.3 on Windows 7, if this makes a difference.

Hello Peter,

I've been trying to add a custom menu to a document. I go through
the motions of adding the menu and saving it within the document,
but when I click on it, or any other menu on the menubar, it is
greyed out. Assigning the menu item to a macro action has no effect
on this.

Could be this menu doesn't work in the chosen part of LO.
Example: There are many menues in a form of Base - but most of them
are greyed ot, because they won't work with a form.

Which menue are you trying to add to which kind of document?

Regards

Robert
- --
Homepage: http://robert.familiegrosskopf.de
LibreOffice Community: http://robert.familiegrosskopf.de/map_3

Hi Robert,

I've tried it for both Write and Calc documents. The menu is a custom menu to add some extra features to the document. As it's a test the assigned macro displays a messagebox. The attached document is a Write document which gives the error - open it and click on any menu item.

Best regards,

Peter
mailto:lo@ptoye.com
www.ptoye.com

I think it's a user interface issue. I've had the same thing with my
macros that I've added to the toolbar. In Ubuntu, the macros are greyed
out, but they work fine. In Windows or Linux Mint, they are not greyed
out. The user interfaces and themes are different between the systems.

Virgil

Virgil,

Odd. It seems that your experience is the opposite of mine, but I don't have
a Linux system that I can try it out on.

OK, I've found the answer from someone on the LO Ask forum (why are there
two?).

It seems that LO doesn't allow you to click on a menu item unless there's an
action associated with it. Seems sensible, but I was designing the user
interface before writing the macros. Once I'd added the actions all was
well, so we can close this thread.