I’m suggesting a major improvement to “Join” to deal with the situations where “Join” fails. “Join’s” current feedback on failure, ie: a blinking surface, is woefully inadequate! after carefully crafting two surfaces and the result of attempting to “Join” them is only a blinking surface is well beyond frustrating!! the three cases I recognize (perhaps more failure modes checked for in the code) are overlap, gap, and non-planer. coding “Join” to display on failure: overlap: x.xxx; gap: x.xxx; or angle: xx.xx would be a simple change AND a huge improvement in usability.
Rhino 8’s current response (notice I didn’t say answer) in my world is a “conclusion” with NO insight provided into cause. it is the poster child for why I’d like to see the code improved! the code almost surely already has a logic tree that checks each of the conditions of interest and aborts with the “conclusion” or moves on to the next check. notice the numeric value of the abort condition is already known (ie: the abort path was selected; “if then else” logic for old timers that remember Fortran 77) so the only thing being requested is a modified message that would include the numeric value & the name of the actual cause…
