I’ve been trying to let Rhino believes that a geometry is moving, but I don’t want to really move it. The purpose is just sending a signal, so the “geometry modified” event can be triggered, or periodic curve won’t break when I edit grips.
My simplest approach is nudge it as small as it can, so it is:
Short answer is - it works every time. But when I ask opinions from LLMs, they all tell me this is dangerous for many reasons (they are bitwise identical, semantic misleading, unstable across APIs, etc).
So, I wonder if this is really the case? Should I avoid doing this?
After testing, I found Transform.Identity won’t trigger RhinoDoc.AddRhinoObject as the way that a real nudge does, unfortunately.
But it did inspire me on the periodic curve case. A straightforward copy of the Point3d works. So, I guess it only monitors if it is still the same struct, it is not based on real location.