Hello guys,
I am trying to use the shatter component and CCX component to split multiple curves up.
The issue i have is that there are some curves missing after the shatter component.
What i derive is that the shatter component only takes the curves that were in contact with the intersection points and if there aren’t any, the curves are subsequently discarded.
How do I retain the curves?
Problem with Shatter.gh (16.4 KB)
Silly me. But I think I was trying to also figure out why the shattering of the curves does not happen at the intersection points and I must have switched the inversion of the E input.
Which brings to the case in point, would you have any idea with regards the the random shattering of the curves ?
Indeed, it is incorrect. Hmm, is there a better method to split these curves up rather than with the CCX component?
Just a additive to dear Jessen script , so we can have them in branches
Thats very clear. I will need to spend some time to digest this to understand the rationale and how to use CCX component properly in the future.
P.S. I found a way by moving forward the Region Difference operation (appeared as Trim with Region) :
This is an example of good intentions gone wrong. In my usual fashion, I saw things in your code that I would do differently and started hacking. I forgot that SrfSplit results need to be sorted, which added unforeseen complexity and is still flawed. 
The Value List (blue group) switches between edges and surfaces.
The two groups of curves in you scene do not full establish intersection points. so I used Null Item to identify the Null data from Curve|Curve , and then used Dispatch to extract them, which are the "missing " curve you mentioned earlier.
Wow, thanks for the efforts! At least it provides me with a better understanding
Thank you. This is also an interesting solution. ! I will analyze.
Thanks for explaining further. I have a greater understanding now on using the CCX component.
