The Grid. The most kicked about lost child of Rhino can and should be made better. It’s current implementation has not changed much since v1 and really is suffering.
I wrote many wishes for the grid but they just fly over McNeel, many times I use different kinds of grids created from geometry under what I am building. Maybe to an average programmer they do not understand, but for a designer of any involved object/s grids and geometrical structures are always used. One only has to look at the literature on the subject:
Classical architecture The poetics of order to see how grids can be used also any books on design be they modern or antique from prehistory to now all show the controlling factors and uses of the grid. Rhino needs to get up to snuff on it’s grids.
We should have:
1.Other grid types that we can define other than current subdivisions,
2.Circular triangular and other geometric types of grids and other types in this vain. Or is this a test command you guys are hiding?
3.Define girds more easily per view and ability to store per named cplane not in options.
4.(Why if I type “Do away” after four it puts a hyper link to yahoo automatically argh) anyway Do away with the grid controls in options and allow per cplane freedom, association naming and objectivity.
5.Allow more decoration of grids in color, line type and labeling.
6.Ability to set where the lines are drawn i.e. if I only use one quadrant of the grid then the grid should reflect that. I usually don’t need the left hand side of the grid I orientate with sections to the object I m working on, locating the cplane origin on the lower left side of the object or it’s first 0,0,0 coordinate therefore I don’t need to see all the other useless lines in the negative quadrant.
7.Symmetry option for modeling needs to get better and be combined with the grid why are we still using archaic methods when all other programs have good symmetry by now.
8.Other users have suggested many other things I wish would make it into grids as well and should be looked at.