[QUOTE=Mambo4;28547]Menu Man can be a beast to learn up front, but it can certainly do what you want.
Depending on the complexity of your customization, you might be able to do it out of the box.
Max lets save all your customization under the menu Customize/Save Custom UI scheme…
at our studio we have a folder of max scripts that live far, far away from the default max folders. ( I hate digging through autodesk’s arbitrary defaults)
We have one maxscript that utilizes menuman to convert individual .ms files into macroscripts in the local user’s max folders and then builds the menus out of them.[/QUOTE]
I have a question regarding this method of menus, I wonder if anyone can help.
I have a wrapper that launches 3dmax by pointing to a custom startup.ms, where I build all my menus. The reason I am doing it this way is because I want to keep the vanilla maya act as if my tools don’t exist. But I have two problems;
1 - Macroscripts gets copied into APPDATA, therefore goes against my whole idea of isolating things. (Not a big deal)
2 - The menu I create with menuMan.createMenu is persistent, it’s not tied to that session, so if you launch 3dmax without pointing to my startup.ms , you still see these menus. This is bad.
Is there any way around my problem n2 ? I want to build my menus dynamically ONLY from my startup.ms and don’t want them around/built any other way
thanks!