When creating a new Rhino file by exporting objects from another file, I don’t knwo what template is used exactly, but I’d like it to be my own template so that I have all my standard layers and annotation styles.
Can this be done ?
Export appears to use the current document properties for the created file. This appears (not thoroughly tested) to be equivalent to deleting everything (including layers) except the selected items and the layers containing the selected items followed by SaveAs.
Note that when a new instance of Rhino is opened (rather than an existing file being opened) the document properties, layer states, etc are set from the template file; the template file is not referenced. Save and SaveAs save the current document properties, layer states, etc, including any changes made since the file was opened. For more informaton see Rhino Template Files
Open a new instance of Rhino with the desired template.
Import the file created by exporting.
Or if the first file is still open, then CopyToClipboard/Ctrl-C the selected objects.
Open a new instance Rhino with the desired template.
Past/Ctrl-V the copied objects into the second instance of Rhino.
Hi David, thanks for your answer.
I know there are workarounds, but I wish it was possible to define a certain template to be used every time a new Rhino file is created, no matter how it was generated.
For example, when you open in Rhino a file which is not a .3dm, but a “supported files” type *, same problem : blank slate !
* you know, the file type at the VERY END of the file type list (god that makes me swear every time !).
A very preliminary conclusion is that when Open is used with a file which is not .3dm or .3dmbak then the document properties, etc are set to “internal defaults” which are the same as when Rhino is opened with “No Template” option (unless there is information in the file which implies a different setting).
Hi David,
So basically, you already asked for this, and the answer was “Sorry, no”.
Great.
Rhino is very often used to open file formats, and is being advertised based on this specific capability.
It would really make sense to add the choice for a template to be up and running directly with a familiar layer and annotations environment.
I’m no programmer, but it doesn’t seem very difficult to implement.