Hi again. :)
I find myself doing a couple of things quite often.
** Firstly, I have a lot of pieces of code that look like this:
... // stuff, possibly modifying menu items
It would be nice if I didn't have to create two menu items. Lots of times I find myself making both objects menu<shared>, which causes a slow resource leak. What I'd prefer is if run_popup took one extra parameter - the index of the sub menu to display as the popup. For example,
** The second thing I do often is modify menu items. I change things such as "show window" into "hide window", etc. The code looks like this:
menuitem_info mii = popup.item_byid(IDM_SHOWWINDOW).text(mbShow ? "Hide &Window" : "Show &Window");
It would make things *much* easier on us menu-editing-types if we could do some in-place menu editing. Maybe an operator that takes a menu item id (throwing an exception if the id is invalid), or something of that nature.
Thanks for your time, I know this was a long post. :)
I have to make it easier not to mistakenly use menu<shared>, when you actually need menu<owned>.
Soon I'll introduce Resource Splitter, where you'll be able to say something like:
Perhaps I can modify the syntax so that you simply can't say:
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.