I’d like to have the splitedge as a flow from getting the isocurve extracted as doing a separate command of splitedge is a bit tedious. Getting the intersection of where to split by osnap is something I’d like to reduce as a step.
As for split… well I don’t use it as much as splitedge… so that I’ll take back.
After doing lots of sweeps for connecting multiblend area I see this to be helpful.
Not saying split edge should be inside and taken out as a command , but just to make better flow of the task…
Hi Toshiaki - so, if I understand… you want the ends of the extracted isocurve to split the edges where it intersects them… . correct? If so, would you want all intersected edges to be split? If not, do we not get into more clicks and UI complication than is maybe worth it?
I suppose splitting all edges would help.
(though I was thinking ability to select which sides was friendlier but this does add much complication…)
Where this wish comes from is the splitting edge to do a sweep2, networksrf, or patch, selecting the point to split and splitting is a bit tedious.
Sometimes need trial and error so need to repeat it couple of times often…
Merging edges is easy to do but splitting needs a bit more work.
Maybe if splitedge would pick out the “point of interest” to split maybe that might help too.
(there would be some problems how to handle end knots… but maybe just for intersection of edge with a
curve, or a point.)