Hi,
I would have expected coerce3dpoint
to be able to coerce a 3DPoint from a TextDot.
I understand it might be breaking current workflows, but it feels as a good powerup for a coercing method.
-Willem
Hi,
I would have expected coerce3dpoint
to be able to coerce a 3DPoint from a TextDot.
I understand it might be breaking current workflows, but it feels as a good powerup for a coercing method.
-Willem
rs.TextDotPoint doesn’t work for you? --Mitch
Hi Mitch,
Well yes it does that is what I ended up using when no 3Dpoint could be coerced from the input object.
The issue I had was that I had to rewrite a script to use dots instead of points (for unrolling with attributes).
The old script coerced a 3D point from a point object and it struck me as odd that a dot could not be coerced into a 3D point.
Thanks
-Willem
I suppose that’s a valid point (pun intended…)…
Sounds like a legit request. I added this to our wishlist at
https://mcneel.myjetbrains.com/youtrack/issue/RH-35577
thanks