Entities selection priority
konstantin_shiriazdanov
Member Posts: 1,221 ✭✭✭✭✭
Recently i notices that some of my FS and standart features suddenly started to only allow Entities of body type if the input field filter has this option among other entity types like faces. This is exactly not how it worked before, and i liked prevous behavior better. Was this intentional global change or it only with me?


0
Comments
-
This was intentional change that was introduced in an effort to improve the selection experience around the split feature. However, there have been enough adversely affected features in other areas that we will be reverting to the old behavior in the next release.
In the meantime, you can use the "Select other" command to select individual entities.2 -
When will the next release come?Evan said:This was intentional change that was introduced in an effort to improve the selection experience around the split feature. However, there have been enough adversely affected features in other areas that we will be reverting to the old behavior in the next release.
In the meantime, you can use the "Select other" command to select individual entities.0 -
-
1
-
That seems to affect also picking an edge in loft (when lofting surfaces)... akward
0 -
-
it works so for all bodies - solid, sheet or wire. entities of body type got the highest priority. possibly priority control could be based on filter order and thus it could be adjusted transparently for each feature, instead of this hidden magic
0 -
-
This should probably be configured in a UIHint:konstantin_shiriazdanov said:it works so for all bodies - solid, sheet or wire. entities of body type got the highest priority. possibly priority control could be based on filter order and thus it could be adjusted transparently for each feature, instead of this hidden magic
what i think the code should look like:annotation { "Name" : "Example Query", "Filter" : EntityType.FACE && EntityType.BODY, "UIHint" : "PRIORITY_USING_FILTER" } definition.exampleQuery is Query;
3 -
@mbartlett21 We agree.
For the upcoming release, we are simply reverting back to the old behavior for all custom features, so the issues described here will be fixed. However, if/when we want FS writers to control this, we'll use an explicit UIHint rather than implicitly encoding the priority via filter order.
1 -
This should be fixed now
Jake Rosenfeld - Modeling Team3






