On Sun, Nov 18, 2012 at 6:05 PM, Art Heimsoth <artst...@artheimsoth.com>wrote:
> > So this could have been:
> >
> >
> > MYMENU_MENU MENUEX
> >
> > {
> > POPUP "&File" IDM_FILE_POPUP
> >
> > {
> >
> > MENUITEM "&Open", MENU_FILEOPEN
> > MENUITEM "&New", MENU_FILENEW
> >
> > MENUITEM "&Save", MENU_FILESAVE
> > MENUITEM "&Saveas", MENU_FILESAVEAS
> >
> > MENUITEM SEPARATOR
> >
> > MENUITEM "Recent", MENU_FILELAST1
> > ....
> >
> >
> > where IDM_FILE_POPUP would be a symbolic ID of say, 150. With the
> > extended menu format, separators can be assigned IDs also and you
> > could remove it by ID without worrying about the position thing.
>
>
> This did not work for me, nor did trying to use symbolic ID for the
> separator menuitem.
> When using symbolic ID on both the POPUP and the MENUITEM statements as:
> POPUP "&File" MENU_FILE -- defined in .h file
> ..
> MENUITEM SEPARATOR MENU_FILESEP -- also defined in .h file
>
> I get an error on the filePopUp~removeSeparator(MENU_FILESEP) statement of:
> Object "0" does not understand message "REMOVESEPARATOR" in UNINIT() of
> Menu class ...
> I get the same error if I use positional syntax on the removeSeparator
> statement too.
>
Sorry, I was a little misleading on that. The entire menu definition would
have to be defined using the extended menu format. Most resource editors
will not use that format. But, I see below you are saying you are not
using a resource editor.
If you are writing the menu definition yourself, I could look up the entire
syntax for you and you could write it out. The reason it is not working is
that you have two different formats mixed togethter.
> If I use positional syntax on both the getPopUp and on the
> removeSeparator, it appears to
> work
>
Yes, that should work.
> but then I get what appears to be trace info:
> In uninit() of PopUpMenu
> In UNINIT() of Menu class cMenu=009B4308
>
Those are some debug statements I had forgotten to remove. You can just
ignore them. They are removed in the next release.
>
> I also tried the syntax in the .rc file of
> POPUP "&File", MENU_FILE
> and
> MENUITEM SEPARATOR, MENU_FILESEP
> note the commas here, and got an error there too, but I think it was a
> different error - I did not
> record it before I tried something else.
>
> I am okay with using the positional syntax, but would like to understand
> better why the
> symbolic syntax does not appear to work. I have been editing the .h and
> .rc files manually
> and am not using a resource editor.
>
Yeah, the reason is as I explained above. The entire menu definition in
the .rc file would need to be consistently in the extended menu format. I
only gave you a few pieces.
--
Mark Miesfeld
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
