Script
By Swordslayer · Credited author: Vojtech Cada · 2024-02-11
Simple dialog that shows all user-set hotkeys in one list. Hovering over each button shows the category and group of the action. Clicking the button executes the action - unless the button shows as disabled, which means that the action is not available (the macro might have got lost or it may belong to a plugin which is currently not installed).
When you run the script, it loads the active hotkey set file. If you want to load another, maybe a hotkey set you've downloaded and want to see what actions are mapped there, there's the 'Load Shortcuts File...' button for that. This way, you will also see in advance all the actions that are not available on your max install. Not all action names are saved in the shortcut file so for some items unavailable on your machine, you might only see a << MISSING >> text - this might happen with some plugins and also with custom quad shortcuts.
Installation: The .ms file can be run from any location (Maxscript -> Run Script...). If you want to put it in toolbar, menu or quadmenu, you can create a macroscript using Macroscript Creator.
Tags: shortcuts, actionMan, hotkeys, hsx, actionManager
obaida · 2024-02-12
Thanks for this great script,
what about a toolbar can it be done through .ms script?
there is couple of plugins adding toolbars, but it's included in .dl* files
Thanks in advance, for all what you add to the community,
Regards.
Swordslayer · 2024-02-13
Technically, you could diff the backup cuix and current workspace one and start with that but there are plugins that create toolbars, menus and quadmenus on the fly and those are not saved there. Plus you already see the toolbars you've added so I'm not sure I follow.
obaida · 2024-02-15
Thanks for the replay,
creating a toolbar through something like startup/CreateToolbar.ms file that can be created on the fly with full list of custom scripts not in manual way, similar to V-Ray toolbar or Corona.
Swordslayer · 2024-02-17
Easiest way is to create a rollout and register it as dialogBar so that it can be docked like toolbars. If it needs to be 'proper' toolbar, check the maxsdk\howto\ui\cuitest sample.
Thanks
obaida · 2024-02-19
yes it should be proper toolbar, thanks for the guide.
Regards.