After migrating my custom grips plug-in into Rhino 6, I find the following problems:
When enabling grips, the owner object keeps being on the scene, which makes it difficult to select grips as there’s continuously interference with it when picking. In Rhino 5 there was no issue with this as the owner object somehow “disappeared” as a pick option when enabling grips.
When moving grips, the owner object is never transformed (I think m_bNewLocation flag is always set to false).
From time to time there’s a crash when moving a grip.
I have these very same 3 problems in @dale 's example SampleCustomGrips. Still, cannot find the real change from 5 to 6 that causes the issue. Any idea?
Hi @dale, I updated the SDK (redownloaded and installed) and it works! So no issue now.
Just one thing, point 1 above
When enabling grips, the owner object keeps being on the scene, which makes it difficult to select grips as there’s continuously interference with it when picking. In Rhino 5 there was no issue with this as the owner object somehow “disappeared” as a pick option when enabling grips
Is there a way to prevent this in R6? In R5 this didn’t happen.
The selection includes the 8 grips. I.e. the owner object (the rectangle) is not included in the selection (though it remains visible).
In Rhino 6 this changes: the owner object remains selectable, so if I make a window selection it’ll include the 8 grips + the owner object.
This is a bit messy sometimes when you precisely want to select grips and not the owner object. Is there a way to prevent the owner object from being selectable once the grips are on?
You can see in the last picture that this makes the selection process a bit painful, as the mouse has to distinguish between the owner object and the grip the user wants.