Marco Musy

Oh maybe it's just this: ```py from vedo import * s = Rectangle().subdivide(5, method=1) s.cut_with_sphere([0.5,0.5,0], 0.5).scale([1,1,1]) s.subdivide(5, method=1) b = s.boundaries() line = Line(b) print(line) segs = b.join().join_segments() print(segs[0].length()) show(s,b,...

Ok, try: ```py from vedo import * b = load("test.vtk") line = Line(b) print(line) segs = b.join().join_segments() print(segs[0]) show(segs, b, axes=8) ``` 

What about this solution: ```py from vedo import * import time square1 = Mesh(dataurl+"dolfin_fine.vtk") square1.subdivide(method=1).lw(1) square2 = Rectangle().scale(0.9).rotate_z(25).shift(0.1,0.3) square2.triangulate().subdivide(5, method=1) square2.c('blue5').alpha(0.5).lw(1) t0 = time.time() a1 = square1.area() a2 = square2.area()...

Hi , sorry I was away! Have you already solved this?

I see. If I understand it correctly the problem is underdetermined in general. One way of "injecting more information" in the system could be to subdivide the line - which...

Hi that happens because the resulting slice is coincident with the plane, so there no way to know which one should be rendered first. In fact I guess you don't...

PS: also consider this approach to do the loop ```py import vedo as vd import numpy as np cone = vd.Cone(pos=(0, 0, 0), height=8, r=2, axis=(0, 0, 1), res=100) cone.alpha(0.8).c('cyan')...

hi, sorry for the late reply... I also tried but could not find a way to make it work.. unfortunately the boolean operations in vtk are a weak point of...

Hi Leon, thanks for reporting, it looks indeed a bug.. Possible workarounds: ```py # import vedo # from vedo import * # plt1 = Plotter(axes=1) # plt1 += Cone() #...