Whoa... no wonder you think it were horribly complicated :cool:
That said, about deleting POPUP menus I have no idea, may need some trick or perhaps not possible at all?
INLINE submenus vanish if they contain no entries anymore, as you noticed too.
I do like that menus don't need to be attached anywhere to still exist, that makes creation a lot easier, no preconditions for the first entry. No need to "create" a menu first, just act as if it were already there, insert your action line, and it IS there
Normal menu lines are easy to delete, just set the label empty.
For an example look at the
native zoom macro, setmenu line 2+3
And I update the names ocasionally too during a session, just set the same command in the same parent menu again just with another label.
I do agree that I often greatly miss syntax *examples* in the wiki too!
Boy, what was it for an endless struggle until I finally figured out what this mysterious $ARG thing means
While in reality it's ridiculously easy. And without examples am never sure where to put " " or not etc. In the end we all do the same, just look for already existing macro snippets and copy their ways.
But that's exactly why it's a pity most menus are created in much more complicated ways than necessary, e.g. first building inline submenus for one single command or such nonsense. And of course the next one takes this as example again and the circle continues, sigh.
====
Your discovery that menu lines can also be deleted by adding a label without an action is news to me, but why not
And that only goes to demonstrate AGAIN just how brilliant setmenu is - you can throw at it what you want and it works!! LOL!
Edited 2 time(s). Last edit at 04/10/2015 07:47PM by siria.