The idea is not bad at all. The only main disadvantage I can see at the moment is that choosing the wrong collection by mistake can potentially freeze Blender. But anyway that is the case already for many operations when the user does something wrong.
This is an interesting UI suggestion.
The newboolean code I have been developing has been written so that it can do a boolean operation on many objects at once – and doing so will be much faster than doing them one after another. So I had been wondering what UI to use to expose that to users. I had been thinking of some kind of list view where you pick objects one by one. But the suggestion here would be easier to implement and has the advantage of also being more comprehensible to the viewer if the collection is large. Since my code does it all at once (and pays not attention to threshold, since arithmetic is exact), order does not matter. Also, intersection and union both work in this scenario.
I don’t quite get what is supposed to happen with the “children” box. Someone please explain.
Nice move. Maybe a “Link boolean objects” would be more clear and let the user avoid the task of parenting everything?
edit: “Link boolean objects” is not a great choice of words. Too vague. It should make clear that it propagates the transforms of the object to all the booleans. You english speaking people find the right words please
yeah maybe a simple operation for workflow practicality as a bonus ? this can be done in python easily.
i don’t know that much on how the main idea is implemented in C, but if the input is just a list of objects then having more options on how to generate this list (collections, children, or even a python API with raw object list, etc… ) don’t cost too much and give more options to the users which is always great imo.
If you have a patch for this, AFWS, please post it to developer.blender.org and tag me as a reviewer. I would really like to do something like this after I have gotten newboolean in master and beaten down any bugs that come up.
I have some projects on Boolean (mostly performance) that will take me a week or two, but after that I would seriously consider working on getting something like this into Boolean, so please do make a patch when you feel ready. Thanks.
Not sure if it’s possible but I feel like most optimal ux is to add children as target option and remove collection input field if it’s selected. Then it’s just one click (or no clicks at all and few ctrl+scrolls)
Having to change target to collection, then selecting children collection option in input and then clicking on children check mark is a lot of setup.
Most common use cases are gonna be:
Target Type: Object
Target: Some Object
Target Type: Collection
Target: Some Collection
Target Type: Children
I think it’s safe to assume what we want to use children of our main object and not something else, so there is no reason to expose input field.