Hi Jason, I have a plan for improving the baking operation, people should be able to set more (if not all) attributes of baked geometry. Layer, Colour, Linetype, Name, even UserText. It will be difficult to maintain source layers, because Grasshopper works purely with geometry, it doesn't care about the myriad attributes that Rhino stores per object. The main problem with your suggestion is that source objects could come from multiple layers, I'm even planning (way down the line) ways to import geometry on the fly from external 3dm files, like referenced blocks. Those objects may be on layers that don't even exist in the current document. I think allowing you to specify a target layer for a single component will solve all these problems in a single stroke, without making the geometry in Grasshopper more memory intensive.
Not sure about the selecting-the-bake-result. I suppose it's pretty easy to add an option somewhere that treats Bake as a typical Rhino command and thus selects the new geometry. There is one more snag about this, Bake at some point will have to option to be automatic. I.e. when you drag a slider the geometry will be baked immediately, replacing the old geometry. Do you also expect it to select the new objects in this case? -- David Rutten [email protected] Robert McNeel & Associates On Jan 18, 6:46 am, jvannest <[email protected]> wrote: > I've looked for discussion on these two wish list items and found > little. These wishes stem from using GH like Generative Components -- > by modeling a component, modeling a larger geometry, and then > distributing the component over the geometry. > > [1] It would be nice if GH remembered the layer of its input geometry. > After deforming and arraying that geometry, I wish GH would "bake" > said geometry back onto its original layer. > > For example, suppose one arrayed cubes (on a "cubes" layer) over a > sphere (on a "sphere" layer). It appears that the bake command merely > deposits the resulting cubes on the current Rhino layer, but it would > be very helpful to have those cubes on the "cubes" layer as one goes > on to further modeling and rendering. > > [2] It would be nice if the items recently "baked" were pre-selected > in the Rhino environment for immediate translation. > > For example, when one uses the [ Dimension -> Make 2d Drawing ] > command in Rhino, after executing the command, Rhino pre-selects the > resulting lines for immediate export or moving. This is so helpful > when comparing iterations of work. > > I imagine that these wish list item involve changes to the Rhino > platform, not merely to GH, thus making implementation complex. > > GH is an awesome tool, and these are relatively minor wishes. Thanks > for your efforts, and know that several colleagues here in New York > are using GH with increasing enjoyment. > > Peace, > > Jason
