[Feature Request] #5972 CompoundFilter items selection helper

[openBrain]

Hi all,
Part CompoundFilter is a nice tool, but especially when used in "specific items" mode, it is really odd to setup. Particularly because you don't know how many fragments are in the compound, and which index corresponds to which fragment.
So below is a proposal that would (I think) help compound filter to be a more user-friendly tool, and probably increase its popularity.

CF1.png (82.71 KiB) Viewed 1019 times

CF2.png (142.91 KiB) Viewed 1019 times

I think mock-up pictures are self-explaining, but feel free to ask for more if needed.

What do you think about that proposal ?

[chrisb]

Good idea. It doesn't have to be something new, it could be an extension to explode compound. Instead of creating all items a selection of the wanted could be made.

[openBrain]

It doesn't have to be something new, it could be an extension to explode compound.

Not sure to fully understand... It's not a new feature, it's just an helper to CompoundFilter. When you click "OK" in the Tasks panel after you selected, it just fills the "items" property of the CompoundFilter.

[chrisb]

Selecting all items is the same as explode compound, isn't it? So it could be sensible to have it there (too).

[DeepSOIC]

Good proposal.

If only there was a way to add that "..." button from python...

Also, your proposal is missing the support for advanced syntax (like "::2" for including every second object), but I guess it's acceptable (user just shouldn't touch it if that advanced syntax is actually needed).

[openBrain]

Selecting all items is the same as explode compound, isn't it?

Yes but no. ExploreCompound will expose all fragments in the tree view as separate objects (inside a "folder" IIRC) while CompoundFilter only shows one object in the tree view.
But I also think that using the same dialog to create a SelectiveCompoundExplode could be a good idea.

If only there was a way to add that "..." button from python...

I wasn't sure if it was possible or not, but my feeling was indeed that it has to be coded in C++.

Also, your proposal is missing the support for advanced syntax (like "::2" for including every second object), but I guess it's acceptable (user just shouldn't touch it if that advanced syntax is actually needed).

I also think it's acceptable because :

• It doesn't break support for advanced syntax (you can still enter it manually in the property field
• It is normal user oriented
• You should rarely have more than 10 fragments, which should make it acceptable to click each needed item

Moreover, I never used advanced syntax mainly because I absolutely don't know in which order are the fragments inside the compound.

[DeepSOIC]

Moreover, I never used advanced syntax mainly because I absolutely don't know in which order are the fragments inside the compound.

You probably never applied it to a Draft Array, for example. Sure, for the output of a BOP, the indexing is relatively unpredictable.

[Kunda1]

Added GH issue number to thread title