Fixed a bug in pymel.core.uitypes.AETemplate.callCustom() that was introduces since Maya 2023 #468
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion that now expects the arguments to be passed in first before adding the callCustom flag. Without this fix, the callCustom() method will not do anything and thus breaking AETemplates that depends on it.
SolenOchHavet
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Maya 2023, Autodesk introduced an undocumented breaking change in
maya.cmds.editorTemplate()for thecallCustomflag. The order the arguments must be passed in has been flipped. Without this fix, thepymel.core.uitypes.AETemplate.callCustom()method will do nothing and thus breaking AETemplates that depends on it.