Summary: This is a new concept of Rhino's wish list add or change anything you like and rate wishes to your personal favor.
This Wiki page is an attempt to organise wishes and to rate them. I am thinking of a system to rate them, do you have a suggestion?
To improve modeling curves, surfaces, solids/polysurfaces, and meshes
|1||01 mar 07||Multiside Surface Match and Splitting||Klemen Tavcar||multi> side surface match (like MatchSrf command with option for 1-, 2-, 3- or 4- side surface matching with at least G2 continuity)||-|
|2||01 mar 07||Multiside Surface Match and Splitting||Klemen Tavcar||auto> extending splitting curves and surfaces||-|
|1||06-Jun-07||Parametric Dimensions||Joshua Shafer||Parametric> dimensions would be nice in order to create adaptable designs, but it should not become the standard practice, only an option. A simple dimension which can be linked to certain attributes; line to line or point to line.||-|
|1||06-Jun-07||Parametric Dimensions||Johnny Chandler||I> too would like to see parametric dimensions. I do a lot of work with Pro-E and would like to at least have the option of changing dimensions as I see them. I would like to stick with Rhino because it runs very well on my laptop and hasn't crashed yet (unlike Pro-E). Based on the features I use of both Rhino and Pro-E, Rhino is much more user friendly and forgiving. The dealbreaker is in the dimension editing. The “scale” feature just doesn't do it for me.||-|
|1||mar 07||Dimension Layers||David Ray||It> would be great to be able to assign layers in Dimension Properties, with separate designations for text and leaders, possibly as a list box of all layers with the top option as “Use Current Layer”. This would allow for different colors and line weights when plotting and allow the user to hide leaders. Sometimes it is necessary to hide leaders to simplify a drawing, such as for laser projection or small labels, but then have them visible on larger, detailed prints.||JS|
|1||apr 07||Mesh tool logic||Olivier Suire||Some> tools that previously worked on NURBs only now work also on meshes. Yet, some other tools like “CurvatureAnalysis” or “ShortPath” are not yet implemented for meshes. I wish they were. I also wish that, when possible, there was not a separate tool for the mesh, but rather an intelligent tool that would adapt it's behavior wether the input is a NURBs or a mesh.||-|