[al] Removed tracking selectability and lock metadata #2075
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.
Previously, AL_USDMaya tracks selectability and locking metadata, but there are few issues for this approach:
ProxyShape::onTransactionNotice()
), thus also making the status out of sync easilyThis PR is meant to change the logic to be "query selectability / locking when needed", it is the most straightforward and accurate way to track selectability and locking.
Notice that this PR affects the "transform chain" (parent transforms that are created automatically when selecting geometry prims, or for those prims that have been marked as "importByDefault" and "needsTransformParent" in schema translators or Python translators) regardless of the viewport mode.