McNeel Wiki

Site Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
rhino:schemes [2023/09/12]
127.0.0.1 external edit 		rhino:schemes [2023/09/12]
127.0.0.1 external edit
Line 1: Line 1:
 ====== Using Schemes to Start Rhino====== ====== Using Schemes to Start Rhino======
  
->Using Schemes to start Rhino with different sets of options on the same computer +>Start Rhino with different sets of options on the same computer 
  
 Basically, Rhino Schemes are just different sets of personalized options that can be called from a specific desktop shortcut.  Pretty much everything in the Options section of Rhino can be stored in a scheme. In this way, Rhino can be started with different combinations of workspaces (*.rui/*.rhw files), languages, colors, etc., just by starting Rhino from the appropriate desktop shortcut. The schemes exist independently of each other, and can be modified. Basically, Rhino Schemes are just different sets of personalized options that can be called from a specific desktop shortcut.  Pretty much everything in the Options section of Rhino can be stored in a scheme. In this way, Rhino can be started with different combinations of workspaces (*.rui/*.rhw files), languages, colors, etc., just by starting Rhino from the appropriate desktop shortcut. The schemes exist independently of each other, and can be modified.
Line 7: Line 7:
 By default, one scheme is always created (Default), and any modifications will automatically get saved to that.  To have more than one scheme, you must specifically create new ones. This page explains how to do that. By default, one scheme is always created (Default), and any modifications will automatically get saved to that.  To have more than one scheme, you must specifically create new ones. This page explains how to do that.
  
-A newly created scheme will always start with the default set of options (as if Rhino was freshly installed).  If you want to duplicate an existing modified scheme, there isn't yet a direct, one-button way to do that.  For this reason, this page also outlines several methods to duplicate existing schemes.+A newly created scheme will always start with the default set of options (as if Rhino was freshly installed).  If you want to duplicate an existing modified scheme, there isn't yet a direct, one-button way to do that, but as of V6 it's pretty simple, instructions further down on this page.  Those instructions also apply to copying settings from one installation to another.
  
 ===== How to create a new scheme and desktop shortcut===== ===== How to create a new scheme and desktop shortcut=====
-//(for Rhino 3 and up)// 
  
 1. Create a new shortcut on your desktop which points to your new Rhino scheme.  The easiest way to do this is to copy an existing Rhino shortcut. Hold the Control key down while dragging the default Rhino icon to a new location on the Desktop, or right-click and copy it. 1. Create a new shortcut on your desktop which points to your new Rhino scheme.  The easiest way to do this is to copy an existing Rhino shortcut. Hold the Control key down while dragging the default Rhino icon to a new location on the Desktop, or right-click and copy it.
Line 19: Line 18:
  
 4. On the Shortcut tab, edit the Target path. Add a switch for the new scheme: \\ 4. On the Shortcut tab, edit the Target path. Add a switch for the new scheme: \\
-//(The example path below is for Windows Vista/7/8, Rhino 5 64 bit. Others are similar.)//+//(The example path below is for Windows 10/11, Rhino 7.0. Others are similar.)//
  
 **"C:\Program Files\Rhino 7\System\Rhino.exe" /<color darkslateblue>Scheme=MyNewScheme</color>** **"C:\Program Files\Rhino 7\System\Rhino.exe" /<color darkslateblue>Scheme=MyNewScheme</color>**
Line 25: Line 24:
 //-- Make sure there is a single space before the **/Scheme=...**// //-- Make sure there is a single space before the **/Scheme=...**//
  
-{{:undefined:rhino7schemeproperties.png?400|}}+{{:undefined:rhino7schemeproperties.png?216|}}
  
  
Line 40: Line 39:
   * **A scheme can include a template specification**, i.e. any scheme can open with a specific template. After starting Rhino with your newly created scheme, use the **New** command and browse to the file you want to be your starting template for that scheme. In the lower left corner of the dialog, check **use this file when Rhino starts**. You can create a custom template by saving a drawing with the **SaveAsTemplate** command or using Save As Template from the file menu.   * **A scheme can include a template specification**, i.e. any scheme can open with a specific template. After starting Rhino with your newly created scheme, use the **New** command and browse to the file you want to be your starting template for that scheme. In the lower left corner of the dialog, check **use this file when Rhino starts**. You can create a custom template by saving a drawing with the **SaveAsTemplate** command or using Save As Template from the file menu.
  
-===== How to duplicate a scheme without editing the registry=====+===== How to duplicate a scheme=====
 //This topic has been updated to Rhino V6 and later !// //This topic has been updated to Rhino V6 and later !//
  
Line 54: Line 53:
  
   * The settings file includes which workspace file(s) should be loaded by a specific scheme, //but it does not modify the workspace files themselves// - that needs to be done separately via Rhino's workspace editing tools.    * The settings file includes which workspace file(s) should be loaded by a specific scheme, //but it does not modify the workspace files themselves// - that needs to be done separately via Rhino's workspace editing tools. 
-===== How to duplicate a scheme by editing the registry===== 
  
-**Note: //<color red>Be extremely careful when registry editing! If you use the above method, this is usually not necessary.</color>//**+  * //(For V7 and earlier)// If different schemes share the same workspace file (.rui), a change made to the workspace by one instance will affect all others that use it!  The workspace file is independent of schemes -- the scheme only knows which one to open, not its structure.  If you have multiple instances of Rhino running, the last instance to close will overwrite the .rui file. So when making changes, it is advisable to have only one instance of Rhino open at a time.  If multiple users are using personalized workspaces, it is best to have separate workspaces with separate names and have each one open with the corresponding scheme.  //The workspace concept has been completely revised for V8, so some of the above may not apply.//
  
-        * From the Windows Start button, choose **Run**, then type **Regedit**, **OK**. +  * It is not currently possible to control the loading or unloading of plug-ins with Schemes.  Plug-ins are either loaded or unloaded globally for all schemes at the same time.
-        * Navigate to //HKEY_CURRENT_USER\Software\McNeel\Rhinoceros\4.0// (or 3.0). +
-  * You will see all your schemes listed there.  Right-click on the scheme key you want to copy, and choose **Export**. +
-  * Place the file where you can find it again, like on the desktop.  The file has a **.reg** extension.  The actual file name is not important. +
-  * Right-click on the .reg file and choose **Open With...** and select **Notepad**. +
-  * Inside you will see many instances of your original scheme name, let's say it's //Scheme: MyCurrentScheme//. +
-  * Using the Replace function in Notepad, replace the phrase //Scheme: MyCurrentScheme// with //Scheme: MyNewScheme//, +
-  * Make sure you replace __all__ instances! +
-  * When that is done, save the .reg file and close Notepad. +
-  * Right-click on the .reg file and choose **Merge**.  When you click **OK**, your data is merged into the registry in the correct place. +
-  * All you have to do now is create a shortcut on your desktop to your new Rhino scheme.  The easiest way to do this is to copy an existing shortcut and then right-click on the copy, choose properties, and change the Target to: **...Rhino4.exe" /<color darkslateblue>Scheme=MyNewScheme</color>** //(or ...Rhino3.exe...)// +
-  * It's a good idea to rename the shortcut so that you know which scheme it will start. +
-  * The new scheme should start from this shortcut with all of the previous settings of //MyCurrentScheme//. +
-  * Change what you want while in this instance of Rhino// (make sure only this instance is running!)//, these changes will be saved under the new scheme automatically.+
  
-> **Note:** //It is not currently possible to control the loading or unloading of plug-ins with Schemes.  Plug-ins are either loaded or unloaded for all schemes at the same time.// 
- 
-> **Important:** //If different schemes share the same workspace (.tb) file a change made to the toolbar layout by one instance will affect all others that use it!  The toolbar layout in the .tb file is independent of schemes -- the scheme only knows which .tb to open, not its structure.  If you have multiple instances of Rhino running, the last instance to close will overwrite the .tb file. So when making  toolbar changes, it is advisable to have only one instance of Rhino open at a time.  If multiple users are using personalized workspaces, it is best to have separate workspaces with separate names and have each one open with the corresponding scheme.// 
  
  
 +>Last edit 12.09.23 by MSH/Helvetosaur
    
rhino/schemes.txt · Last modified: 2023/09/12 (external edit)

Page Tools

© 1997-2024 McNeel • North America • Europe • Latin America • Asia • Korea     Recent Changes RSS Feed Driven by DokuWiki