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

HierarchyStandardModel: invalid icon filepath? #9

Open
csaez opened this issue Sep 4, 2018 · 2 comments
Open

HierarchyStandardModel: invalid icon filepath? #9

csaez opened this issue Sep 4, 2018 · 2 comments

Comments

@csaez
Copy link
Contributor

csaez commented Sep 4, 2018

Hi,
I'm not sure if this is a bug, but while trying to make the HierarchyStandardModel icons work today I realized that the running code is moved to pxr.UsdQt namespace after build, leaving the icons behind (pxr.usdQt) and making the relative paths to fail.

ArcsIconPath = 'icons/arcs_2.xpm'
NoarcsIconPath = 'icons/noarcs_2.xpm'

Is there any plans to integrate the use of resources with the build system? Or even better, moving to QResource?
Is this something we can help with?

Cheers!

@nrusch
Copy link
Collaborator

nrusch commented Sep 5, 2018

Hi @csaez, thanks for the heads-up. We aren't using the icons internally, so I hadn't run into this one. It doesn't look like they're being installed at all by the build process, so that would definitely be one of the first things to fix.

I also think it would be great to avoid hardcoding paths to resources into code, so I would be in favor of moving to QResource. If you're interested in tackling that, or have already done it internally and are able to submit it back as a PR, I think it make a welcome addition.

@csaez
Copy link
Contributor Author

csaez commented Sep 6, 2018

Hi Nathan,
This is not an issue for us at the moment as I followed your advice moving to a subclass of HierarchyBaseModel (thanks!).

I will keep the move to QResource in mind moving forward tho 👍
Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants