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

Updated Sub layer dialog to display the correct relative path when enabled. #2990

Merged

Conversation

AramAzhari-adsk
Copy link
Collaborator

No description provided.

@seando-adsk
Copy link
Collaborator

@pierrebai-adsk Can you have a look at these changes as well? You have done most of the relative path work.

@seando-adsk
Copy link
Collaborator

@AramAzhari-adsk If only the comment in the .py file is removed, there is no need to re-run the preflight again.

.staticmethod("getPathRelativeToMayaSceneFile");
scope s
= class_<UsdMayaUtilScope>("Util", no_init)
.def("IsAuthored", UsdMayaUtil::IsAuthored)
Copy link
Collaborator

Choose a reason for hiding this comment

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

For the life of me, I cannot figure out why clang-format decided all this needed to be reformatted. The rules are so obscure!


if (!relativePathAndSuccess.second) {
TF_WARN(
"File name (%s) cannot be resolved as relative to its parent layer directory (%s), "
Copy link
Collaborator

@pierrebai-adsk pierrebai-adsk Mar 30, 2023

Choose a reason for hiding this comment

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

This function is general, so I would think we should not mention "parent layer" in the error, just "target directory" maybe? (It's not "parent" either since it failed to be made relative...)

@@ -77,6 +77,12 @@ MAYAUSD_CORE_PUBLIC
std::pair<std::string, bool>
makePathRelativeTo(const std::string& fileName, const std::string& relativeToDir);

/*! \brief returns relative path of a layer file to its parent layer's directory
*/
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here, the doc should not refer to layer, IMO.

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 think the error and docs are minor enough... not sure if it is worth re-spinning another version.

@AramAzhari-adsk
Copy link
Collaborator Author

@pierrebai-adsk I took notes and will keep a commit to be checked in in the future alongside refactors / relative path work.
Thanks.

@AramAzhari-adsk AramAzhari-adsk added the ready-for-merge Development process is finished, PR is ready for merge label Apr 3, 2023
@seando-adsk seando-adsk added the adsk Related to Autodesk plugin label Apr 3, 2023
@seando-adsk seando-adsk merged commit 7c95d14 into dev Apr 3, 2023
@seando-adsk seando-adsk deleted the azharia/MAYA-128453/sublayer-file-browser-unresolved-path-fix branch April 3, 2023 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adsk Related to Autodesk plugin bug Something isn't working 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