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
