For sure I am doing something wrong, I copy-pasted the cs and when I run it does nothing.
(implementation in Rhino 8 would be ideal for people like me that are not good with programming)
The part I don’t see is how you define the source and target “boxes.” I quote these because they are really a collection of 8 points that define a closed volume. A twisted box for example. You can prompt the user to pick 16 points; seems clunky.
What I mean, is that If you input the Reference Box and the Target Twisted Box, and 3 points on both, there’s enough information, the other points get deduced.
This is indeed what I am looking for, but I am under the impression that if a face of the Box/TBox is specified (by 3-4 points), the additional 4 points can be determined by some “edge analysis”.
Here are some possible steps:
Specify 4 points that create a face:
If I consider point 0.
Then check for the points which 0 is connected to: and those are 1 and 3 and 4.
But 1 and 3 are already specified at input
therefore, point 4 is what I need.
Yes, CageEdit is also very similar.
But, instead of having one cage generated by CageEdit over some geometry, the user can select one initial Box and one Twisted Box to act as modifier.
There is a difference though, with Morph (this is what I am looking at as reference for this idea) , the geometry can stick outside the boxes, with CageEdit the geometry cannot stick outside the cage.