- at first I said I'd use this in a new feature, and I was answered that I'm going way too fast.
- So I said I wouldn't use it, and would just add it to make the Editor's code more flexible, and now I'm being told that if it's not used, it's useless.
Seriously. It's just submenus
. You see that in every
application in the universe.
And it's been tested, since I've created a dummy submenu.
So what should I do now? In the meantime, people are compliing C++ assembly classes and porting stuff to Mac, and I can't even commit a bloody submenu.
I didn't see that post, only tzachs' and Monkey's.
Either of us would be happy to review your changes and see if they are worth integrating into the dev branch
Calin, I'll send you a patch file in PM.
To answer tzachs' and monkey's question: I haven't decided if I'll use it myself, but it can totally be used by plugin developers: If they want to add several entries in the menus without bloating them, they can group them in a submenu. For example, imagine if features "check out" and "check in" were grouped under "source control" -- monkey wink wink nudge nudge -- that would be cleaner. That's just an exemple, I'm not planning on developing a source control plugin, by the way.