The RDK Render Content Editors display objects called Render Contents and allow the user to edit them. These editors are all based on a similar interface with only small functional differences between them. Render Contents are the foundation of the RDK core and one of the most important objects it provides. Please see Render Content for more information. The Texture Editor is known to users as the Texture Palette but programmatically it is an editor just like the other two.
- Navigation controls similar to those found on a web browser.
- Resizeable Floating Previews.
- Configurable thumbnails with multiple sizes and styles.
- Resizeable preview pane.
- User interface for editing render content parameters (AKA fields).
- Breadcrumb navigation control similar to those found on file explorers.
- Task menu for performing actions on render contents and setting editor options.
These editors are integrated with Rhino’s tabbed pane system. You can access them through the Rhino Render menu, the Rendering tool bar, or the editor commands.
Lists of materials, environments, and textures are stored in the Rhino document. Each editor displays the relevant render content type as preview thumbnails.
Contents display an interface below the preview thumbnails in an area reserved for collapsible UI panels. An addition to the basic UI panels, several additional collapsible panels are provided by Rhino within the same area as the content UI. These include the Name, Notes, Texture Summary, Local Mapping, Graph and Adjustment panels.
Each material, environment or texture can have child nodes (AKA child slots or sub-nodes). The children can be of any content type, but specific child slots will only support specific types. The most common child type is a texture. For example, the Color child slot for a Custom Material will only support textures, as will the Background image child slot on a Basic Environment.
