Separate callbacks for Save and Export #1226
Merged
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
fowlertADSK
commented
Mar 1, 2021
|
@fowlertADSK I restarted your preflight since the other one timed out and failed. |
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.
The function that gathers the stages that might need to be written out has logic in it to check if we are doing Export vs. Export Selected, but the check for that state is incorrect. The MFileIO::exportType check only tells us what option the last Export ran with and isn't changed when doing a Save. We never want to check if something is selected during a Save, but it doesn't look like there is an explicit state kept by Maya so here we just create separate callbacks so we can keep track.