your answer stimulates some thinking:
you write about “add functionality” - but it is more individual / team-wide drawing-rules:
If you give some rules to your draftsmen “use the companies template” /“don t add layers” / “don t sort layers”, you ll get what you want. Many times i love the creativity of mapping a workflow to what is possible within the rhino-Toolset. Which piece of information is mapped to wich structure / name / group / layer / userText / color … in a document. And i love all those possibilities we are “allowed” to do with rhino / the interface.
But imagine the complexity of an interface, that includes options to set up limitations: - do not use Mesh-Data, do not use Control-Point-Weight, do not use object-Color Yellow, do not use curve degree 4, … and so on.
But there is some functionality missing:
it would be nice to have some kind of Layers.Sort( Comparison Delegate ) - Function in Rhinocommon. This would allow an easy Function “resort Layers against Dan-Summers-Company-Standard” - Or is there any option to sort the Display-Order of the Layer-Palette via Rhinocommon at the moment ? - haven t found it.