Hi Sam, that's right. The SDK does not provide methods for that. Adding such features will require the coordinated efforts of a large part of the Rhino core team, automatically putting it on the long term list. Once auto-baking is implemented in Grasshopper, then we start to get a number of limited options. I can easily enough capture selection/ deselection events coming from Rhino, and then compare the altered object to a record of Grasshopper objects. This will allow for a 2-way connection between Grasshopper selection states and Rhino selection states. But it would not work for anything that is not baked.
-- David Rutten [email protected] Robert McNeel & Associates On Feb 11, 3:14 am, SamR <[email protected]> wrote: > David, > > #2: Is there no way you could implement a mouse-over type link between > grasshopper 'geometry' and the related component? Out of my league, so > i'm just casting straws here. > > Sam > > On Feb 11, 6:44 am, David Rutten <[email protected]> wrote: > > > Hi Gijs, > > > #1 You mean you want the Grasshopper preview to match exactly the > > current display mode that a viewport is in? > > > number 2 is completely out of the question I'm afraid. You can only > > select objects in Rhino that are part of the document. Grasshopper > > geometry doesn't actually 'exist', so Rhino is completely unaware of > > it. For this to work, I'd have to add all Grasshopper geometry for > > real, causing memory usage to explode because of the use of Attributes > > and Undo records. > > > -- > > David Rutten > > [email protected] > > Robert McNeel & Associates > > > On Feb 10, 10:34 am, Gijs <[email protected]> wrote: > > > > What I would like to see in GH is: > > > > - all display modes available that are normally available in Rhino, so > > > including the ones we make ourselves > > > - be able to select the geometry in the viewport, in order to see to > > > which component it is connected > > > > -- > > > Gijs
