Taz, Visose, that indeed sounds like an easy fix. I'm not too fond of this particular solution since it might involve some data duplication (the display code still tends to duplicate data in order to prevent null points during viewport redraws, but this is something I'm looking into).
Taz, do you really need this kind of control on a per-parameter basis? Would it be enough to be able to 'attach' some sort of properties override object to an entire component? -- David Rutten Robert McNeel & Associates On Sep 28, 1:14 am, visose <[EMAIL PROTECTED]> wrote: > What taz explains about the layers parameter and component is exactly > what i visualized that didn't seem to require a big change in how > grasshopper works, just another component. Add rhino layers as another > type of object to be able to link from the rhino model just as curves, > points, etc. The next best thing would be to link materials, and be > able to change some of it's basic properties through grasshopper. I've > read that the main users of grasshopper are architects. Architecture > is not only geometry, but also texture, light and color. Make that > parametric too, please ;)
