I have a wish that I really want you to consider:
One problem with Rhino for drafting right now is that we have to make custom display modes to get descent output results, but these display modes are NOT stored in the file. So if I want to send my Rhino file, or store it for backup, then I have to export the display mode used as a unique name and store it together with the file and instruct any new users to install that display mode IF they want to view the files as intended (Which is cruzial if changes are going to be made and updated drawings are to be outputted).
Make Rhino’s default display modes hard coded so changes to them are stored in Rhino as alternatives.
And if these are used in the file then they are stored in the file too.
These variations are shown in the pull down menu for display modes alphabetically under each main display mode.
Finding a good way to organize them and to handle how they are stored in the file.
Why is it important?
Being able to open a file on your laptop and continue to work with the SAME looking display mode as you used when the file was built on an other machine is much more important than you think.
We have just started using display modes in Layout Details in real projects now, and this situation pops up all the time, and dealing with different versions of same named display modes are cumbersome and a problem when we quickly want to make changes to a layout if we are not on the correct machine.
And when we send the Rhino file to a client then we just can’t instruct them to install display modes etc. for it to be shown correctly.
So to sum it up:
I want the default display modes to look the same on ALL machines, and if you make changes to them then those changes are stored as a new sub-name/alteration to the original and saved IN the Rhino file (and in your Rhino app for use in other files too if you want that)
Hope this all makes sense and please ask if there is anything not clear.