Nested Boolean Grouping Manager

Nested Boolean Grouping Manager
Its defining feature is "nesting." It nests Boolean results in the form of a list, enabling "local" Boolean results. It also offers an ultra-fast response time of 1–2 seconds, along with free switching between real-time and manual modes.

I know you will definitely ask me why I developed this.
Because Nvil's Boolean_Stack feature is too basic and too limited, and I have personally tested modo's "pp_MOP_Booleans" plugin and Blender's "bool_tool" plugin. The result in both cases is a very painful and frustrating experience: once the model's polygon count is too high, even a slight change in position forces you to wait 5–8 seconds for the Boolean result to be recalculated, and more often than not you need to wait even longer. But I just want to drag things left and right to adjust the model's position. I just want to see the result at different positions because of the uncertainty in the design process, yet this slight adjustment of vertices, before I have even adjusted them to the ideal position, starts making me wait several seconds, which completely ruins my mood.

Development origin
I developed it in the Python bundled with Rhino 7, and throughout the whole process I told my ideas to "DeepSeek AI."

Why not continue developing in Rhino Python?
Many functions for polygon operations are not available in Rhino itself, and personally I like using Nvil, because it has been with me throughout my long-term work. After using the built-in Boolean_Stack, I found it unsatisfactory. I hope my "Nested Boolean Grouping Manager" will help it grow and bring it a major upgrade. I personally think this is feasible, and I am very much looking forward to it...

Alright, below is the Python source code and video demonstration I am sharing. I am giving them to you, and I hope they are helpful to Nvil. May Nvil keep getting better. And to you, programmer, I hope you have a pleasant day today.


https://vimeo.com/1226192394?fl=ip&fe=ec

https://youtu.be/aJEOT-K_PpU

1. IStonia, Happy Mid-Autumn Festival~ Today is the Mid-Autumn Festival. I'm very glad to communicate with you again ^_^
2. "Nested Boolean" is about lists calling and using each other.
3. For example: during the first Boolean operation, it needs to calculate all the faces of the source sphere. Let's say it has 5 million faces—pretty scary, right? So it will be very laggy.
4. During the second Boolean operation, it only calculates the small local region left after the result of the first Boolean, so the Boolean response speed will be super fast.
5. Below are the screenshots and annotations I provided.
6. Please take a look at them in order.
7. That's the core of it.

Yeah, hope you have good time!

You can achieve that within one group.
https://youtu.be/zZ6cg8b_fhM

Oh, I only followed your first video to operate. I've never tried adding a third object consecutively in a group list. By the way, by the way, it works now. You're awesome.

I encountered the following problems:
1. After the "Boolean Stack" graphical interface is launched, can it be modified so that it does not keep hogging Nvil? Because users still need to operate and work normally...
For example: objects such as "Geometry→Create→Create GeoSphere" in the top menu of the Nvil main interface cannot be created normally.
For example: the custom shortcuts of "StreamLine Tools" all become invalid ("point", "line", "face", "move", "scale", "rotate", etc. all need to be manually clicked on the corresponding panel buttons, which will reduce work efficiency).
2. It would be even more perfect if all buttons of "Boolean Stack", including the Boolean type modes in the context menu, could have customizable shortcuts, making it convenient for users to focus on perspective view work without having to go back and forth clicking panel buttons, which would reduce work efficiency.
3. In "Boolean Stack", when the user selects one of the source objects in the list, the other loaded source objects are first hidden (but not including the Boolean result object), and only the currently selected source object is activated. In this way, the perspective view will not be too dazzling because many objects exist.
4. In "Boolean Stack", only when the user selects one of the source objects in the list should the corresponding one be highlighted, while all source objects remain highlighted all the time, because it is inconvenient to distinguish which one is in the activated and selected state.

Try this.
NVil-Sep-26-26-Steam.zip
https://1drv.ms/u/c/2266374caf942d48/IQAbHPSO-9OUQ7SrHst5b8tMAdPW-NPevvOORn77JdHxmhI?e=saSBJe

https://youtu.be/rLyBThLWSCA