-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maya: Allow specifying raw JSON custom tools menu for Maya. #356
Maya: Allow specifying raw JSON custom tools menu for Maya. #356
Conversation
The toggle overrides which one of the two to use. It uses either the settings UI builder OR the JSON menu. It does not merge the two in any way. If anyone is in dire need of having this there and like this 'implementation' in settings then would be great to see that transferred. We don't use Nuke so won't be amongst my needs. |
Wouldn't be better to use enum? So user can see only one of the inputs when selected... |
If there's a way to have the settings front-end to switch between one of the two. Yes, 100%. Any examples? |
When enum has |
…ancement/maya_settings_add_json_menu_option
Thanks you very much - this is much better! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried with the latest commit of the branch and it installs the custom tools as expected(tested with both menu builder and full json definition). I like this one better than the last one as it allows user to be clearer which options to use to define my custom tools.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested successfully in Maya 2023.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we get the addon version incremented?
…ancement/maya_settings_add_json_menu_option
Done with 590f1db |
Changelog Description
Adds support for specifying the raw JSON for custom tools, allowing much easier/better access for complex menus.
Additional info
The non-JSON menu builder in settings also disallows the creation of submenus by its design (as far I could see) and 'pasting' our existing settings from e.g. OpenPype didn't allow it to automatically create the required structure for supporting submenus, etc. because of it.
By having this raw JSON field I could just copy-paste our OpenPype settings for the custom colorbleed menu for our Maya.
Testing notes: