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.
Feature
Here's a quick test to get mouse clicks in the viewer to be able to select prims inside the view - porting some of the functionality from USD View itself.
Note however that since it relies on USD View's data model it requires
pxr.Usdviewq
and thus this particular data model can't be used with e.g.usd-core
. For this prototype it's not an issue because this currently only applies to the viewer widget which itself can also only work if that library is present.Nonetheless for #25 we would need a data model that can be shared between all widgets. The question then becomes whether we want to completely roll our own data model so it can be separate from
pxr.Usdviewq
dependency or unfortunately maybe make the USD viewer a requirement itself.@Sasbom with this PR you're at least able to click around in the viewport to e.g. select some prims and then press F to frame selected or A to frame all.