HI ,
quick question : on massive GH definitions it usually happens that its hard to detect which "selectable preview component " is ON…as a result I end having previed geometry that i wont to turn off on rhino viewport but i struggle in order to find to which “selectable preview component” it belongs to.
is there a way to click the shown geometry and easily intercept which component on the canvas is generating it ?
thanks
What I do to structure previews along the definition path is grouping:
Put all stuff you want to preview at a certain stage in a group (blob or rectangle style) and then make a scribble, call it preview 1, preview 2 etc. And also add that to the respective group. I usually try to collect all sliders in one column, so I place the preview group scribbles there too for quick access
On a “preview” group, you can then right click, and go “select all” and toggle preview on/off.
Hope this makes sense 
Hi and thanks , yes it helps but its not a solution ,
i do something similar but every once in a while , usually for debuging purposes i end dropping some selectable preview component along the defition and, on long projects , once i am done with the task i sometime struggle to find which component is generating the preview.
i think a “reversed” way to work , meaning for example that : 1 you select the “selectable” geometry on rhino viewport , 2 you push RBM and select for example “highlight father” or similar , would be appreciated
Navigating on large definitions can be a pain… and I like your idea.
One way to do this is by using a script to extract the component nickname which you need to set so it is unique or at least somewhat distinguishable if you have many of the same components.
In my test, the box component nickname is then baked with the geometry into a layyer called temp.
Using the search function in Grasshopper, you can search for the nickname. It works also if you move components around so the coordinates in my sample script may be useless. It’s just a quick test I did based off another example and with the help of copilot.
I think if I implemented saving nicknames with geometries, I’d save the nickname as user attribute.
nickname_cache.gh (9.8 KB)
HI Martin and thanks for your suggestion.
yes i am actually renaming different components or also groups in order to allow me using searching native filter in grasshopper , its a possible solution and also a good habit because it forces me to organize the definition and keep it clean and ordered.
that said i think that the “reverse search” as i suggested could be very useful for the selectable preview component
I’ve used the plugin years ago too.
The new component is in Rhino 9 WIP but it doesn’t work the same
