How to find names of (context) menus

When trying to customize Opera's menus I find it difficult to determine, which of the 277 menu sections in the copy of my standard_menu.ini is applicable for the menu I'm going to edit. In order to identify the menu names I added dummy submenus to each menu, e.g.

[Link Popup Menu]
    SubMENULABEL,[Link Popup Menu]
    ...
    ...

This produces (unclickable) labels and basically I'm happy with the result. Using "SubMENULABEL" instead of the standard "Submenu" makes it easy to comment out these added lines (Search SubMENULABEL / Replace with ;SubMENULABEL).
What I still don't like is the right arrow, the submenu indicator. Looks ugly and is a bit irritating. Misusing the arrowless "Item" for my purpose would be much better, but no matter how I try, "Item" always results in an enabled menu item, which I find much more irritating. Does anybody know a way to get rid of the arrow somehow?

Just in case somebody is curious how to add above extra line to each menu section (and to remove them later): It's simple with an editor that supports regular expressions. I use Geany that came with my Linux, but for Windows Notepad2 will do as well. Regular expressions are very powerful and allow document-wide changes with one click in the Search/Replace dialog. I also use them to indent all lines except the menu headers, which makes the menu.ini file much more readable in Opera's source editor. I've included some syntax examples in the customized file standard_menu_labeled.ini. Syntax may differ slightly for other editors.

Originally posted by mochikun:

Does anybody know a way to get rid of the arrow somehow?

An enabled item is not really the problem, since the Submenu can also be selected — the access key is the real problem. Try this:

Item, "& *** LINK POPUP MENU ***"

Since the space is the access key, pressing space will dismiss the menu, but the existing access keys are not changed.

Find "Item, & " and replace with ";Item, & " to comment out the headings.

Originally posted by Pesala:

An enabled item is not really the problem, since the Submenu can also be selected

Submenu cannot be selected here. The disadvantages of using enabled items would make them a bad choice:

                                Item enabled   Submenu disabled
________________________________________________________________
Selectable via mouse                   Y              N
Selectable via up/down keys            Y              N (Windows:Y)
Visual feedback on mouse hover         Y              N
Dismisses menu                         Y              N

Originally posted by Pesala:

the access key is the real problem

I guess in real life access keys are not relevant, If they were, you probably would have fixed your own menu (The letter "O" is assigned twice and "Open in New Tab" is originally accessed with letter "P"). Normally it's not worth the trouble to fix them. Just deleteting one menu item may change all other access keys ... you'll get mad chasing all changes. BUT: In this special case I like your idea to designate a fixed key because it's so easy and it effectively avoids duplicate assignments by the OS. Not the space key though, since Linux has problems and doesn't hide the "&" marker, but the left square bracket is fine:

SubMENULABEL,&[Link Popup Menu]

The base menus are all pretty simple (in English anyway). They're all whatever was clicked on followed by "Popup Menu", except for the one you get when clicking on a text selection - that's the "Hotclick Menu" (in reference to the fact that double-clicking a word will normally display this menu as well as selecting the word). Anything that's a submenu or part of a menu can be arbitrary if they chose to (though that would make maintaining the menus pretty hard), but base menus have to be named as they are.

Maybe I've been here too long, but to me the names are all pretty obvious. Though if all else fails you could check this list ...

Originally posted by sgunhouse:

that's the "Hotclick Menu"

that's the "Hotclick Popup Menu"

Though if all else fails you could check this list ...

But I don't have to guess and I don't have to check long lists since I have the names already as labels in the menus. And there is another advantage - though this is probably not for everyone: I keep a customized menu file in my profiles directory, holding only the customized menu sections. Since Opera pulls whatever it can't find in my customized menu.ini from its default standard_menu.ini, I previously found it hard to determine, if a menu is already customized and therefore can be found in my customized menu file or if it is still part of the pristine default file. By using different labels in both files - [menuname] and [menuname]_edited - I know not only the names, but also the source.