As you can see, after curve Separation, one copy of the curve is created and one …origin with no segments!
Curves, not segments. Select all points and Shift-D. Move apart and P on selection - that will be two separate curves in one object where P works.
Thanks eppo, in what cases exactly it works, to separate curves previously joined?
I also have two objections (to developers):
-
If Separate doesn’t work on segments, then it shouldn’t be available on segment level or an error message should appear.
-
For consistency and intuitiveness, Separate should also work in segments by replacing the commands you mentioned. One word vs a sequence of commands.
It does not need to be joined before; just click Alt-C on default Cube with Delete/Only Faces before. It is converted and contains several curves in it. Try the same on the Monkey.
That separation level most likely would be hard to achieve. For instance, i could separate several cylinder or monkey loops (as a new object) and convert them to Curve object. In Curve edit mode i would have to analyze that. While it seems like simple job, i can bet there would be cases where CPU will get some 10 degree temperature increase doing that. As to the segments - what if you select odd number of points somewhere in the middle of one curve ? Or you would like to see them break into single point objects?
Commands i wrote before were just to get the working example of one Curve Object containing several separate/not connected curves in it.
Useful to know, thanks.
The behavior I’d expect and the solution is the following:
It would search for sequential selections and then make a new curve for each sequential selection it finds. Then optionally, would build one or more curves with the remaining segments. That would eliminate the need for error messages nicely, ie if you skipped intermediate segments it will just make more curves. It would also cover the single-point curves: You’d just have to select every other segment.