Selection by kind #641
Merged
Selection by kind #641
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
July 9, 2020 11:40
Defined a "UsdSelectionKind" option var to control the selection behavior. If the option var is assigned with a non-empty string to indicate a Kind token, the nearest ancestor that is assigned with that Kind token or a subcategory of that Kind token will be selected when a prim is picked in the viewport. If the prim doesn't have any qualified ancester, it falls back to the default behavior which will select the exact prim (can be slower due to walking the hierarchy). If the option var is undefined or empty, the default behavior will be used to select the exact prim. For details about Kind, please refer to "Kind : Extensible Categorization" (https://graphics.pixar.com/usd/docs/api/kind_page_front.html#mainpage_kind). Examples: // Select the nearing ancester which is a model or its subcategory. optionVar -sv "UsdSelectionKind" "model"; // Select the nearing ancester which is a group or its subcategory. optionVar -sv "UsdSelectionKind" "group"; // Select the nearing ancester which is a user-defined kind or its subcategory. optionVar -sv "UsdSelectionKind" "user-defined"; // Select the exact prim that is picked in the viewport. optionVar -sv "UsdSelectionKind" "";
Closed
Closed
|
From a usability perspective, it appears to work as advertised. 1) select by component
2) optionVar empty ( select prim ) Thanks, @HdC-adsk ! |
kxl-adsk
approved these changes
Jul 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The pull request is to add a "UsdSelectionKind" option var to override selection
behavior (GUI support is coming separately).
The default behavior is to select the exact prim which is picked in the viewport.
If the option var is assigned with a non-empty string to indicate a Kind token,
the nearest ancestor that is assigned with that Kind or a subcategory of that
Kind will be selected when a prim is picked in the viewport. If the prim doesn't
have any qualified ancester, it falls back to the default behavior (but it can be
slower due to the cost of walking the scene hierarchy).
If the option var is undefined or empty, the default behavior will be used to
select the exact prim.
For details about Kind, please refer to Kind : Extensible Categorization.
Examples:
// Select the nearing ancester which is a model or its subcategory.
optionVar -sv "UsdSelectionKind" "model";
// Select the nearing ancester which is a group or its subcategory.
optionVar -sv "UsdSelectionKind" "group";
// Select the nearing ancester which is a user-defined kind or its subcategory.
optionVar -sv "UsdSelectionKind" "user-defined";
// Select the exact prim that is picked in the viewport.
optionVar -sv "UsdSelectionKind" "";