At the points were the tangent curve meets the circles i can controll the blend input to soften/add fillet to the tangent curve.
What I would like to do is to controll the blend of the tangent curve at the points at the inner and outer cirles sepparately, to have one blend value at inner circle points and one blend value at outer circle points. To achieve something like this:
Instead of splitting up the circles into 50 segments and making one big curve through all the points, just make the smallest repeating unit: One half of one scallop. Get the tangents at the two end vertices, scale them appropriately then use Bezier Span or Nurbs Curve to make the S shape. Mirror it about the X axis and polar array 50 times, then Join Curves.
Things like this I would normally first formulate on a rectangular strip, and use one of the morphing tools (here, Flow) to turn it into a circle. It’s computationally more heavy, but, I think, easier for a beginner to understand.
There is just no logic to keep from doing illogical inputs. For example, the sum of the geometry does not allow to circles to have tangents. I would not call it “breaking”, just input error.
When I actually wrote software for a living, coded all sorts of checks to make sure folks could not do that, GH to me is sort of like programming without easily created safety nets.
I guess a person could write a “scribble” saying “If the circles disappear, adjust inputs until they reappear”
Since I am pretty new at GH stuff, what IS the method for input error checking?
Here is another issue, as I see it. Not knowing how large anyone is going to make anything, setting reasonable ranges is not possible.
You can do some conditionals on inputs, (> < = regex etc) and then switch a Gate to a disconnected output if the input is out of bounds, but it gets tricky if you actually want to catch the error and display a message.
I hear ya Tom, but like I mentioned in an earlier post, people using one of these GH definitions can and will set up their own ranges for what they are working on and suddenly all those boundaries have to be altered too. Messy, very, very messy. Unless of course, we decide these are not supposed to be commercial grade applications to be run by someone with virtually no idea of what they are doing. That is sort of my take on these. . . .
