generative modeling for Rhino
UPDATE since release 0.8.0064: this is now resolved by the Entwine component
24th idea: add number of items input to Point CP component
the component should ask you the closest now many points you want, and the hook should be set to 1 by default
say you want the 5 closest points, you input 5, and you get them, no more sort list etc...
not to be picky, but i think the Closeses PointS component would be enough if it's default value would be 1 (just to tidy things up a bit more)
25th idea: wire visibility registered in the wire, not in the hook
when one uses wires, it's usually because the component that is needed for input is quite far in the definition. it can be the case that that information needs to go into another component, and you move the wire accordingly, but the visibility remains in the hook so you have to change the wire visibility on two hooks.
26th idea: set wire visibility to Hidden when holding alt and dragging the wire
pretty self-explanatory.. (works with the idea above)
27th idea: radio waves on output hooks that have hidden wires linked
it's nice to know when you see a component that has one output hook with apparently nothing linked to it, if that's really the case or it there's a hidden wire linked to it (this again works together with the idea 25th idea)
28th idea: when "preview selected only" is activated, show the selected geometry regardless of the preview status of the component
i usually use this preview mode when i try to find specific elements in the definition, usually when something doesn't work right. Sometimes the "suspects" have the preview disabled and i would like to skip the step where i have to enable the preview of the component in order to see the geometry when preview selected only is activated.
29th idea: component to extract the lowest/highest n numbers of a list
no of items to extract
(+ lowest items indexes)
(+ highest items indexes)
would be easier then using the sort list + sublist, what i usually o