This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Maya: Add Validate Frame Range settings #2661
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
It is safe as they do not share the same context. Syncing the settings is tricky and currently we are just consider both of those plugins as separate code (and they are). There are some cases you want them to be separete and you'll probably find as many cases when it is better to have them in sync. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Brief description
Add Validate Frame Range plug-in to settings to allow to disable it, toggle whether it may be optional, etc.
For some projects we'd prefer it off by default since many instances are published at different lengths.
Additional question
I noticed there was another Plug-in with the exact same class name ValidateFrameRange for the Standalone Publisher. What happens in that case? How do the Settings match to a particular Pyblish Plug-in?
Would this introduce a conflict now? Or is this safe for the Standalone Publisher as is?