Add backwards compatibility and remove "visibleOnlyInFrameRange" #250
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
- The "visibleOnly" option was included a lot longer but never actually worked as it was a remainder from an older pipeline version. With this change things work again as they used to in the ancient pipeline. - It removes the redundant "visibleOnlyInFrameRange" which was implemented to do exactly what the "visibleOnly" originally should have done. This corrects that and deprecates "visibleOnlyInFrameRange"
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.
renderglobalsDefaultinstances onuseCustomFrameList.visibleOnlyInFrameRangein favor ofvisibleOnlyas that did nothing before and was intended to be used for exactly this behavior. This fixes it, while maintaining backwards compatibility for the instances that still have thevisibleOnlyInFrameRangeattribute.