Thanks for the suggestion. That did compile vusrs15.0.0.6i but it didn't add the menu entries to _mdi_menu.
Did you figure this out?
I just did some tests. In the help file on menus, it says you can create a menu in a source file and then "run the macro" to apply the resource change. It doesn't say what "run the macro" means. I suspect if you "insert" the mdi menu into a .e source file, edit it then load it using the load command, your changes will take effect.
From testing I found that if you edit the mdi menu in vusrs15.0.0.6i.e, then use the menus command on the macro menu and edit the mdi menu, you will see you changes there and if you click ok (you might first have to change something in the menu editor), it will load a new menu with your changes. This takes immediate effect on the menu bar.
Alternatively, if you edit vusrs15.0.0.6i.e then types its name on the status bar to execute it, slick does execute defmain but because defmain is empty, nothing (much) happens and slick doesn't realise your configuration has changed. Even if you do save-config, slick won't update your configuration. To get the configuration change flags set you need to do what vusrobjs.e does and add
defmain()
{
_config_modify_flags(CFGMODIFY_RESOURCE);
}
Then if you run the macro and do save-config, slick will save your changed mdi menu. However, slick still doesn't change what appears on the actual menu until you close and re-open slick, or you use the menu editor to reload the menu.
I think if you use the load command to load a source file with a menu in it, slick saves the menu source in vusrobjs.e. Slick also generates a file called userMenus.xml in your configuration folder - dunno what that's for.
Slick V15 also allows you to export your customised menus in tools -> options -> import/export. Slick V14 didn't do this.
Graeme