Custom behavior in general is pretty limited in RhinoCommon. Please help me understand what you are trying to achieve and I can then figure out a solution or at least tell you in is not currently possible.
Implementing it with conduits, but I need to understand how can I implement selection of the objects.
Of course perhaps the best current option is just to use GH to create immutable objects. Here the selection in 3D is still an issue. I know @DanielPiker has a grab tool but I don’t know what/how he did it. Also, I don’t use kangaroo but, I think it only selects vertices, and only if the solver is running.
It definitely seems quite a lot of work if there is a need of hovering (enter/leave) and selecting events implementation on conduits (by a beginner coder like me).
I need some guidance on where to start.
I wanted to start with a point but apparently even that is not working as I thought it would.
What I was trying to do is create a new type deriving from Rhino.Geometry.* I was trying to override the Rhino.Geometry.Point.Transform Which is a method of GeometryBase.
Problem was I didn’t want to store and check for GUIDs every time I try to move something.
I will try now to create a custom class derived from one of the Rhino.DocObjects.* classes and see if I can “negate” the effect of transformations and “explosions”.