You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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 topxr.UsdQt
namespace after build, leaving the icons behind (pxr.usdQt
) and making the relative paths to fail.usd-qt/pxr/usdQt/hierarchyModel.py
Lines 279 to 280 in 35b01ea
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!
The text was updated successfully, but these errors were encountered: