By default, the TestEditToolPaletteCollection editor presumes you have a Rhino for Windows rui file you would like to convert. This launches a developer tool similar to the Command Editor where tool palette collections can be created, organized, and saved to plist files… (You will need to type the entire command it will not autocomplete). Enter the TestEditToolPaletteCollection command. Open Rhino - if it is not already open - and start a new modeling window. If you already have an existing rui file from Rhino for Windows, this job is even easier: you can import that rui and convert it to a plist. If not, don’t worry: creating a tool palette collection is relatively easy. #Rhino for mac layout how to
If you are familiar with the Command Editor in Rhino for Mac, you are already well on your way to understanding how to create a custom tool palette collection for use in your plugin.
The third and final step is to tell Rhino for Mac to load the tool palette from the appropriate file when your plugin is being loaded.Ĭreate or Convert A Tool Palette Collection. plist in your plugin project as a resource. The first step is to create (or convert) a tool palette collection that calls the appropriate commands - or to convert a Rhino for Windows. There are three steps in creating and loading a tool palette collection for your plugin in Rhino for Mac: If you do not yet have a plugin, please begin with the Your First Plugin (Mac) guide. In Rhino for Windows, this UI is normally stored in an rui file that includes the buttons, the icons, and their associated commands. This guide presumes that you have a RhinoCommon plugin that has commands that can be run from a tool palette.
0 kommentar(er)
