Thus, the RUI file will not load if you re-install your plugin. The logic is if the user closed the file, we don’t want to keep loading it every time Rhino starts.Īlso note, if you uninstall your plugin and manually close the RUI file, within Rhino, you are telling Rhino you no longer want to auto-load the RUI file. If a user closes an RUI and the RUI file is associated with a plugin, the file name goes on a list so that Rhino does not automatically open the RUI file in the future. Note, there is additional code in Rhino that saves the name of RUI files closed by the user. You can revert to the original, or default, RUI file by deleting the RUI file in the %APPDATA% folder and then and restarting Rhino, which will cause the file to be staged again, as the file no longer exists. It is copied, or staged, to ensure that the file is writable and to provide a way to revert to the original, or default, RUI file if needed.
If it is found, it is copied to the following location and opened: %APPDATA%\McNeel\Rhinoceros\\UI\Plug-ins\ The first time a plugin is loaded, Rhino looks for an RUI file with the same name as the plugin. If you give your custom RUI file the exact same name as the plugin RHP file and install it in the folder containing the RHP file, then Rhino will automatically stage it to a writable location and open it the first time your plugin loads. For details on creating toolbars, see the Rhino help file.
You can save your custom toolbars in your own Rhino User Interface (RUI) file. If you want to create Rhino-style toolbars, then use Rhino’s Toolbar command. How can I create one or more toolbars for my plugin, and how can I deploy these toolbars with my plugin? Answer This guide covers the creation and deployment of plugin toolbars.
0 kommentar(er)
