Hi @Johnny Matthews (guitargeek) I wonder what's the exact use case you wrote this node for? Isn't it easier to drag and drop curve objects(with one spline in it) into a node tree than blindly trying to set the right spline index?

In D12079#311969, @Miro Horváth (dreamak) wrote:

Hi @Johnny Matthews (guitargeek) I wonder what's the exact use case you wrote this node for? Isn't it easier to drag and drop curve objects(with one spline in it) into a node tree than blindly trying to set the right spline index?

Some ideas:

• You have multiple splines that are interchangeable in a single curve and you want to select one of them or one of them at random.
• Animated lightning. Where each spline is a shape of a bolt. then you could keyframe the spline number.
• Another might be where you have a single curve object and you just want to pull out a single part of it
• Reordering the splines in a curve without changing the original. Curve => Multiple Spline Extracts => Reordered into a Join Geometry

There is some overlap with nodes like point geometry delete, etc. And I'm not totally convinced that an index input makes more sense than a selection attribute input, but generally I think the node is reasonable.

I think I'd remove the "Recenter" feature though. That should be solved more generally with a way to sample a single location from the spline and then a transform node (another thing that would work perfectly with the fields proposal!)

Maybe the use cases could be part of the patch description.