This shows you the differences between two versions of the page.
ja:rhino:hiddensecrets [2014/04/18] |
ja:rhino:hiddensecrets [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Rhinoの隠れた秘密====== | ||
+ | |||
+ | **Dozens of tips and shortcuts** from Rhino experts to facilitate common tasks and save you hours of time! | ||
+ | |||
+ | < | ||
+ | This page needs to be updated for Rhino 5 | ||
+ | </ | ||
+ | |||
+ | =====1. The TAB direction lock key:===== | ||
+ | |||
+ | Once you have made your first pick inside a command like **Line** or **Scale**, if you hit the **TAB** key before your second click, it constrains the direction to an axis between the first pick point and //the mouse cursor position at the moment you hit the **TAB** key// | ||
+ | |||
+ | =====2. Dynamic Camera Manipulation===== | ||
+ | **[[CameraManipulation|Page with explanatory animations]]** | ||
+ | |||
+ | Drag with the RIGHT mouse button in conjunction with **Ctrl** and **Shift** keys to pan and zoom. Dragging the RIGHT mouse button alone rotates or pans the view. If you have a ' | ||
+ | |||
+ | The **Camera** command (keyboard shortcut **F6**)gives you the option to Show or Hide the // | ||
+ | |||
+ | =====3. The Dragmode command===== | ||
+ | |||
+ | with the UVN option locks Ortho to Surface U and V instead of CPlane X and Y when dragging surface control points. Don't forget to reset **Dragmode** to CPlane when you want the default behavior back. | ||
+ | |||
+ | =====4. Selection filters===== | ||
+ | |||
+ | You can filter selection with keyboard (command line) filters in many cases- the most useful is **crv** for filtering curves. Example: if you want to trim with an edge curve rather than the entire surface, start **Trim**, then at the prompt to select the cutting objects, type **crv** and Enter. Now if you click on the edge of the surface, the edge curve will be selected as the trimming object. There is no need to **DupEdge** to get a curve in place of the edge to trim with. If you use this a lot with the Split command, you can create a macro like this (works only with the surface to split being pre-selected): | ||
+ | |||
+ | =====5. Render previews===== | ||
+ | |||
+ | In the basic Rhino renderer or Flamingo the **RenderPreview** command makes a quick and dirty rendering that is very useful for seeing lighting, color and composition without waiting for a full rendering. Use **RenderPreviewWindow** to render just a section of the viewport, it's even quicker. | ||
+ | |||
+ | =====6. Trimming===== | ||
+ | |||
+ | While trimming lines, use **Fillet** with radius 0 to trim and join corners. Since **Fillet** remembers its settings, and you are likely to use fillets more often than chamfers, it may be more convenient to use **Chamfer** for this trick, setting both distances to zero and let **Fillet** remember the radii you are actually using to fillet with rather than revert to zero each time you make a sharp corner. V4 has the **Connect** command to take care of this. | ||
+ | |||
+ | =====7. | ||
+ | |||
+ | Dragging a Rhino-openable file onto the taskbar button of a running Rhino instance or into a Rhino window presents you with a dialog with choices **Open**, **Insert**, **Import**, or **Attach**, just choose one and **OK**. | ||
+ | \\ | ||
+ | As of XP SP 2 and later versions of windows, you can no longer drop your files directly onto the taskbar button. | ||
+ | |||
+ | > **New:** //In V4 and V5, you can drag and drop [[developer: | ||
+ | |||
+ | =====8. | ||
+ | |||
+ | Entering a numeric distance after selecting the start point in the **Line** command constrains the length of the line, whatever location you choose for the end point. | ||
+ | |||
+ | =====9. | ||
+ | |||
+ | You can save and restore Rhino workspace settings using a **scheme**. Basically, schemes are Windows Registry Keys (reg folders) that contain: | ||
+ | |||
+ | * Command defaults; | ||
+ | * Dialog box positions; | ||
+ | * All settings in the Rhino Options pages such as aliases, appearance and colors settings, mouse settings, render settings, shortcut keys; | ||
+ | * Recently-used file list; | ||
+ | * The Workspace (toolbar collection) used and its layout. | ||
+ | |||
+ | * **//Whether Plug-ins are loaded or unloaded cannot be controlled via Schemes//** | ||
+ | |||
+ | To save a scheme, create a shortcut with the destination " | ||
+ | |||
+ | HKEY_CURRENT_USER\Software\McNeel\Rhinoceros\4.0\Scheme: | ||
+ | |||
+ | If you're familiar with it, you can use **regedit** to edit your information directly in the Windows Registry. It's possible to create any number of different shortcuts/ | ||
+ | |||
+ | <color darkslategray> | ||
+ | |||
+ | **[[rhino: | ||
+ | |||
+ | =====10. | ||
+ | |||
+ | One extremely obvious thing that many people have overlooked in the past (myself included) is that if you drag select to the **left**, creating a **crossing box** (dashed lines), anything you touch will be selected, even if the entire object is not enclosed by the selection square. | ||
+ | |||
+ | > **Comment: | ||
+ | |||
+ | =====11. | ||
+ | |||
+ | Right-clicking on an object snap checkbox makes the clicked one active, all the others become unchecked. Holding down the Alt key temporarily suspends Osnaps without unchecking any boxes. | ||
+ | |||
+ | |||
+ | =====12. | ||
+ | |||
+ | Using the Arrow Keys to incrementally alter the view from any viewport is a great way to move about complementing the more fluid dynamic pan used by alt-clicking in the perspective view. | ||
+ | |||
+ | Arrow keys can also be used for nudging, that is to say, moving objects and control points incrementally a controlled distance. | ||
+ | |||
+ | |||
+ | =====13. | ||
+ | |||
+ | Using the Home and End keys to **UndoView** and **RedoView** respectively is a great way to go back and forth along the view history. | ||
+ | |||
+ | =====14. | ||
+ | |||
+ | Make the unfilleted shape and get all the surfaces to Join together to make a closed polysurface. | ||
+ | |||
+ | Make the largest-radius fillets first with the FilletEdge command, selecting all the adjacent edges you want filleted at that radius in the same operation. | ||
+ | |||
+ | Make the smaller-radius fillets, including all the adjacent edges that need rounding (possibly including some edges that were made by the larger-radius filleting). | ||
+ | |||
+ | You can also fillet all the edges of a solid at once with the same radius by starting the command and window selecting the object. | ||
+ | |||
+ | **[[rhino: | ||
+ | |||
+ | =====15. Toolbars can be hidden/ | ||
+ | |||
+ | // | ||
+ | |||
+ | Default is the workspace or ' | ||
+ | |||
+ | <color darkslategray> | ||
+ | |||
+ | //-Toolbar Toolbar Enter Toggle Toolbarname Enter Enter// | ||
+ | |||
+ | For entire workspaces you can use Close or Open : | ||
+ | |||
+ | //-Toolbar // | ||
+ | |||
+ | > **New:** //In Rhino V4, you can right-click in a blank spot in the toolbar docking area to display a list of toolbars. Click the checkbox to display. Also a Lock Toolbars checkbox is at the bottom of the list.// | ||
+ | |||
+ | =====16. Use the Dot command to attach visible labels to your objects===== | ||
+ | |||
+ | Use the pre-numbered dots 0-9 or just the **Dot** command and type your own text. These are all in the **Annotate** toolbar. Dots have the advantage of always being parallel to the view plane and the same size, no matter which way the model is rotated or zoomed. | ||
+ | |||
+ | > **New:** //In Rhino V4, double-click on a text dot to edit the contents. You can use this to add text with spaces- add a dot with any text, double click and add the text with spaces in the edit box, no " | ||
+ | |||
+ | =====17. Use the CheckNewObjects command to detect errors as objects are created===== | ||
+ | |||
+ | This command is a tool to find bugs that create invalid geometry in the model. It is disabled by default. | ||
+ | |||
+ | To enable it, type **CheckNewObjects** at the Command prompt. | ||
+ | |||
+ | This feature makes it possible to find and fix the cause of bad geometry entering the model. | ||
+ | |||
+ | If you are comfortable helping us debug Rhino (and find bad objects for your own purposes), please enable this feature. | ||
+ | |||
+ | How CheckNewObjects works: | ||
+ | |||
+ | Every time an object is created or imported from a file, Rhino runs the Check command. If Check determines that the object is bad, Rhino displays a dialog box informing you of the problem. This message will appear once for each bad object that is created. | ||
+ | |||
+ | Check is a time-consuming process. It can make importing files and working with complex solids somewhat slower. If you find that it slows Rhino down too much, you can disable it by typing CheckNewObjects at the command prompt. | ||
+ | |||
+ | **[[rhino: | ||
+ | |||
+ | =====18. Using PictureFrames as background bitmaps: | ||
+ | [[rhino: | ||
+ | |||
+ | Some advantages to using PictureFrames- | ||
+ | |||
+ | * An unlimited number of images can be placed in the scene. These can be viewed in any and all viewports. | ||
+ | * Images can be scaled and rotated as needed, unlike BackgroundBitmaps which align only with the cplane | ||
+ | * Images can be dimmed and/or made more or less transparent | ||
+ | |||
+ | A possible disadvantage is that there is no guarantee that the image will always be behind everything in space- [[rhino: | ||
+ | |||
+ | **[[rhino: | ||
+ | |||
+ | |||
+ | |||
+ | =====19. Getting the best display of background bitmaps: | ||
+ | |||
+ | **[[rhino: | ||
+ | |||
+ | |||
+ | |||
+ | =====20. Use FullScreen Mode to present a design: | ||
+ | FullScreen fills the monitor screen with the viewports, hiding menus, status bar, toolbars, command prompt, and windows title bar. Press ESC to return to normal view. | ||
+ | |||
+ | The hyphenated version adds command line options. | ||
+ | |||
+ | < | ||
+ | This is some <span style=" | ||
+ | </ | ||
+ | |||
+ | |||