Poor Documenation for new menu system

[TurboChiken]

I can't use Max 2025 until I can learn how to translate my menu-building maxscripts to work with the new menu system. I used to be able to create a new action item to add to a menu using menuMan.createActionItem macroName macroCategory, where the last two parameters were just strings that pointed to the macroscript I had created. But now to create an action item, you need a tableID, whatever the heck that is, and there's no explanation how to get from a macro name to a tableID. 

[istan]

Have you also found this?

https://help.autodesk.com/view/MAXDEV/2025/ENU/?guid=menu_system 

Could give you an idea about using it in MXS..

[ads_decatae]

Thank you very much @TurboChiken. Your feedback is much appreciated. The team is working on improving the documentation, and it will soon be updated.

The tableId for macroscript action is always '647394'. The macroscript action itself will be identified by its actionId in that actiontable, which is constructed of the action name concatenated with an apostrophe and the macroscript's category.

newSubMenu.CreateAction "0C4D0C3D-D870-476A-9CDD-B6ED35A580C0" 647394 "MXS_Demo_Action_Item`Menu Demo Category"

You can find a full example in the following document:

 https://help.autodesk.com/view/MAXDEV/2025/ENU/?guid=GUID-FF48D0EC-6669-4EC7-AB43-E9998A14A198

I hope that helps.

[denisT.MaxDoctor]

О! It's so easy. You only have to remember the action ID..... "0C4D0C3D-D870-476A-9CDD-B6ED35A580C0", for example. And use it later wherever you need it. 😄

[istan]

---

@denisT.MaxDoctor wrote:

О! It's so easy. You only have to remember the action ID..... "0C4D0C3D-D870-476A-9CDD-B6ED35A580C0", for example. And use it later wherever you need it. 😄

---

But it took AD only a year to invent this coding improvement! 😁😁😁

[klvnk]

yeah, they had a look at the "genius" that is Microsoft COM/OLE and thought yeah lets have some of that! absolute nuts

[pi3c3]

I have mentioned many of the problems in the beta. The order of execution is broken as well. If you create an .ms file that generates a bunch of macroScripts for you in your userscripts then the menu won't recognize them. The reason is because the menu creation is the first thing that runs and only after that it will generate .mcr files. So basically tries to add non-existing actions to it. After the restart it works fine... It's just... Annoying...

I have never seen such a cumbersome system...

A simple properly structured .xml would do the trick. -.-