This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
rhino:settingstransfer [2015/09/14] |
rhino:settingstransfer [2023/09/13] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Transferring Personalized Settings====== | ||
+ | >How to transfer all your personalized settings from one installation to another | ||
+ | |||
+ | =====Where are my settings stored? | ||
+ | |||
+ | > Note, toolbars are separate from settings and will be covered further on | ||
+ | |||
+ | In Rhino V5 and earlier most of Rhino' | ||
+ | |||
+ | In all cases, there is not one single file that contains all Rhino options and personalizations. | ||
+ | |||
+ | **For V6 and later - //within the same version// | ||
+ | The easiest way is to simply copy the // | ||
+ | |||
+ | > Note - the location for these files mentioned above is a folder hidden by Windows by default. You can access this quickly by hitting the Windows Start button and typing **%appdata%** and Enter which gets you to " | ||
+ | |||
+ | **For V5:** | ||
+ | To transfer the bulk of your settings, use the Rhino command **OptionsExport**, | ||
+ | |||
+ | Display modes are included in OptionsExport and OptionsImport in V5, and also in the settings .xml files from V6 on. In V5, you can only import all of them at once (or none) via OptionsExport/ | ||
+ | |||
+ | =====Toolbars===== | ||
+ | |||
+ | //**Note on V8**: The entire toolbar structure and arrangement has been completely re-written for V8. V8 no longer uses .rui files, the new format is .rws (Rhino Workspace). Rhino 8 can however import .rui files from V7 successfully in most cases. As soon as V8 is more or less finalized, I will update this section with detailed information on the V8 workspace structure procedures for transferring settings.// | ||
+ | |||
+ | Separate from the other options, workspace files contain most of the info for toolbars/ | ||
+ | |||
+ | // | ||
+ | |||
+ | |||
+ | The workspace file does not contain the on-screen locations for the toolbars however, only the toolbars themselves and whether they are open or not. In V5, location info is still stored in the registry; in V6 and later it has been moved out to an .xml settings file called // | ||
+ | |||
+ | // | ||
+ | |||
+ | To load an existing workspace file in a new installation, | ||
+ | |||
+ | It is possible to import an .rui file from a previous version of Rhino via the above procedure; note however that many things change from one version to another, so this may not always be 100% successful. | ||
+ | |||
+ | Finally, there are some other things that might have been personalized/ | ||
+ | |||
+ | |||
+ | =====Umm, that sounds complicated, | ||
+ | |||
+ | A general transfer procedure might look like this: | ||
+ | |||
+ | **In the old install:** | ||
+ | |||
+ | V5 only: **OptionsExport** - creates an .ini file | ||
+ | |||
+ | V6 and layer: Make a copy of your settings-Scheme_Default.xml file | ||
+ | |||
+ | * V6 and V7 - make a copy of your workspace (.rui) file if you customized it. | ||
+ | * //V8: Workspace transfer procedure to be announced// | ||
+ | * Make copies of any custom template files you created | ||
+ | * Make copies of any other external files used, including: e-maps, scripts, etc. | ||
+ | |||
+ | |||
+ | **In the new install:** | ||
+ | |||
+ | V5 only: **OptionsImport** and import the .ini file created above | ||
+ | |||
+ | V6 and later: //Replace// the existing settings-Scheme_Default.xml file with the one copied from the previous install | ||
+ | |||
+ | * Copy your workspace, template, emaps, scripts, files to appropriate locations. | ||
+ | * V6 and V7 - go to // | ||
+ | * //V8: Workspace transfer procedure to be announced// | ||
+ | * Install any plug-ins that Rhino did not automatically transfer | ||
+ | * Set Rhino up to open with your custom template. | ||
+ | * Set file paths to scripts, templates, etc. if they are non-standard. | ||
+ | |||
+ | |||
+ | //Last edited 13.09.23 MSH/ |