Forward compatibility for Gaffer 0.59's Attributes.extraAttributes
#4049
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
…tes` The type is changing from AtomicCompoundDataPlug to CompoundObjectPlug. This commit must be reverted after merging forwards to `master`.
themissingcow
approved these changes
Dec 3, 2020
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.
This adds the forwards compatibility in Gaffer 0.58, for the changes that #4047 makes in Gaffer 0.59. The type of changes in
TypedObjectPlug.cppare not something I would normally entertain, but there was a limit to what could be achieved in the more usual startup compatibility shim. I think this is OK, because the TypedObjectPlug changes will be very short-lived : I will remove them as soon as we merge forwards to the master branch.