🚀 go-pugleaf

Anyone having problems using the menu editor in the WhiteWater Resource
Toolkit? I'm seeing two distinct nasties that make it distinctly awkward
to use:

1. If I mark a menu item as 'gray', it comes out grayed and disabled in the
   app's menu as it should. But when I re-edit the menu, WRT shows its status
   as being 'grayed' (note the 'ed' on the end). And the menu item is now
   drawn in normal text and is active.

   They seem to have got both 'gray' and 'grayed' defined in the status list,
   and only the former one actually works....

2. I can define a menu so that the popup from the menu bar has an item with a
   sub-popup, like this:

          menu_bar_item
            sub_item1
            sub_item2
              sub_sub_item1
              sub_sub_item2

    and it works fine. But if I extend the menu to have an item _after_ the
    one with the sub-popup, like this:

          menu_bar_item
            sub_item1
            sub_item2
              sub_sub_item1
              sub_sub_item2
            sub_item3

    Then again it works fine, but on editing the menu a second time 'sub_item3'
    (and any item following at the same level) gets moved to the menu bar.

Bug (1) can be circumvented by the app using EnableMenuItem() to _ensure_
the menu is OK if I forget to correct the introduced bugs, but (2) is a bit
nasty to do inside the app.

I'm using what's probably the first release of WRT (we ordered it as soon as
the Windows 3 version was announced). Anyone know of a later version or a 
patch to fix these problems?

Thanks,

Alan Phillips
Lancaster University, UK