Hi All. Does anyone have any insight into how LB identifies vector segments with the cut tool?
I haven’t noticed a pattern or vector characteristics that control whether the cut tool isolates the candidate segment to what I’m hoping for, versus when it ignores that crossing vector. When the latter happens I have to insert nodes at the intersections and either delete the node segment or switch back to the cut tool.
I’m working my way around this map, trimming the overlapping vectors (overlapping a rectangle frame). Most work just fine, but several of them don’t work. Here is an example. Note the proposed cut operation extends past the intended vector intersection.
It’s an interesting question that I’m also interested in. I use the scissor tool a lot and like it very much, but like @tbeaulieu I experience the same malfunctions sometimes and haven’t been able to find a connection that explains it.
It’s also difficult to provoke the phenomenon, in my example of shapes that are both closed and open, all segments are (can be) correctly cut at the nearest intersection of another line.
In this case using edit nodes tool is best. You may need to add a point to define where your line stops and starts so the cut tool knows where to snip.
I’m going to go out on a limb here and say no… no, there is nothing wrong with the shapes. We both just reproduced the scenario in 30 seconds. I’m going with … it’s the app. LOL.
