SUBMENU/MENU SET MenuHead$, MenuItem$, Option$, View$

#Enable/Disable or mark/unmark or remove a menu item.
#Option$ = "Disable|Enable|Mark|Plain|Remove"


Have you tried to write SUBMENU SET MenuHead$, MenuItem$, Option$, View$?

You dont need to write here "remove" you only need to say disable? If this is not possible, then you have found a bug

Hi Lelldorin.

No, disabling won't do it for me, I actually need to remove. What I am setting up is a list of recent files to be re-opened. So this is changing all the time and I actually need to wipe out that (sub)menu each time a file is opened or saved-as, and then rebuild the (sub)menu. Works fine when Recent.. is its own main menu item, but when you try to put it on File|Recent... it does not work

In fact, in my yab documentation MENU SET has the options "Disable|Enable|Mark|Plain|Remove" but SUBMENU SET only has "Disable|Enable|Mark|Plain", so I guess it is not a bug, but a design decision somewhere along the way.

I'm a week or so away from releasing my text editor. This will be as yab code only, for the benefit of others who might want to incorporate a text editor in their projects. Then I will move on to more interesting things: a MarkDown-compatible version with MarkDown itself built-in!! After that, the same thing for Txt2Tags.

No problem, submenus can be removed now.

I still have a bug in my new attribute code. As soon as I get around fixing that, yab 1.7 will be released.

Just to confirm that I understood correctly, the direct support for extended attributes will be available in the next Yab release, right?

right.

I would like to ask if there's any progress?