Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAYA-114041 - As a user, I'd like my pulled Maya object to inherit visibility #2964

Merged
merged 5 commits into from
Mar 30, 2023

Conversation

vlasovi
Copy link
Collaborator

@vlasovi vlasovi commented Mar 23, 2023

Add a custom attribute "combinedVisibility" to proxy accessors to output combined visibility to maya pulled prims

// Remember the path for which we are accumulating the callbacks
MDagPath ancestorPath;
MDagPath::getAPathTo(obj, ancestorPath);
_ancestorCallbacksPath = ancestorPath.fullPathName();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What will happen if the proxy shape node is renamed? Or any of its ancestors are renamed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just tested: renaming proxy shape node or any of its DAG ancestors works fine, as in this case we call updateAncestorCallbacks on the next dirty callback. However, after renaming a USD ancestor of a pulled node we loose the connection inside ProxyAcessors and this is a general problem that exists for all proxy accessors, including relaying the 3d transform. I think we may need to create a Jira ticket for that one.

Copy link
Collaborator

@pierrebai-adsk pierrebai-adsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the behaviour when nodes are renamed.

pierrebai-adsk
pierrebai-adsk previously approved these changes Mar 23, 2023
…validation

- Fixing proxy accessor autotests by doing strict filtering of dirty plugs.
@vlasovi vlasovi added the ready-for-merge Development process is finished, PR is ready for merge label Mar 29, 2023
@seando-adsk seando-adsk added the core Related to core library label Mar 30, 2023
@seando-adsk seando-adsk merged commit c9143f2 into dev Mar 30, 2023
@seando-adsk seando-adsk deleted the vlasovi/MAYA-114041 branch March 30, 2023 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Related to core library ready-for-merge Development process is finished, PR is ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants