Hi ,
Could you give us the option to import Custom Toolbars, Keyboard Shortcuts, Aliases, Custom Display Modes when installing the WIP?
And also for Grasshopper the Userobjects would be useful.
Thank you!
It would be nice if all of this was stored in a local folder and automatically read in by referencing a folder.
And for companies this could be a read-only feature where everybody would read in the display modes, toolbars, templates etc once linked in as a corporate folder.
That way IT could just add or adjust the content and everybody is updated 
So then we would have: Vanilla Rhino installation -(if present) corporate settings and overrides - (if present (custom settings and overrides)
4 Likes
Hi @Holo , having one folder is indeed good, I would put that in my Dropbox.
But even better would be to have a Rhino cloud storage. For userobjects and python scripts it would be amazing, with the option to share all across computers.
And once one loggs in to a different computer everything gets synced: options, UI settings, gh and scripts.
Oh, and also custom textures would be nice to sync.
The library of textures that rhino has is not good because the textures cover a small area and become repetitive. For example, a brick texture should not have 4x4 bricks, it should have a larger surface of 50x50 bricks. A grass texture should cover at least 15meters x 15meters…etc
@CallumSykes is doing some really nice work in this area, I’ll let him chime in
4 Likes
While on this topic, it would be really great if there was a way to automatically update custom toolbars imported from Rhino 8 so all the icons and commands are Rhino 9 commands.
I have a large middle mouse toolbar and I updated it manually. Took a while. If there are people out there with a lot of custom toolbars it would be a huge hassle.
Hello all,
Coudn’t agree more with most of the requests here
Yes.
There is a command PreviousOptionsImporter (announced here) which will import all of your stuff from previous installs on win or mac.
It copies absolutely everything, so it should just work™. I haven’t tried this with the existing toolbar system, but it works for the new one I’m writing and hope to release soon.
1 Like
I would really like to improve the ability to have other sources for settings and have them sync’d to a Rhino Account. 
2 Likes
What do you mean by this Max? All Rhino 8 and 9 commands will have the same command name/macro. I’d love to understand so I can offer something.
Would be nice to have the option to import them when installing a new Rhino. Not all at once, let the user select what it wants to bring form the previous version.
Also having a command is a very good idea.
This feels to me somehow like an different vesion of Package Manager to which users can publish their scripts and userobjects. (Right-Click, Publish - from Grasshopper) or Drag and Drop for other scripts. Once they are there others can search and “install” them.
The search could be by user name, and script name and description…
Once someone finds the user, it can see what that user has published, there shoud be a version or a date…
I will be watching this closely. We will be upgrading from Rhino 7 to Rhino 9 when it is released, and I need to be able to share my setup with 200+ computers across 4 countries. This needs to be as painless as possible.
The icons are different.
And there are examples where buttons on standard menus are a little different even if the underlying commands are the same. SubD hard crease and subD soft crease used to be separate buttons, for example, now they’re right and left click.
None of this is that big of a deal for me, but I could see offices that have built sets of custom toolbars having a bit of an issue.
1 Like
under mesh tools they are separate.
I think the new color logic for the buttons makes a lot of sense. It groups them into categories.
No pressure then!
In theory you should be able to run OptionsExporter and give people that .rhs file and they can import it by drag dropping it into their Rhino and restarting. I say in theory because whilst I’ve tested it, I haven’t tested it with 200 people across multiple languages yet.
Ah right-o! I gotcha. This won’t exist 7 (or lower) → 9, but I would imagine 8 → 9 should because 8 had the concept of “diffs” which whilst causing lots of problems did in theory separate the original and the changes made to the original. The only proof of course is trying out the WIP when I release the new system and seeing how it works for ya.
1 Like
I’m getting “Could not back up settings, nothing will be imported” when attempting import settings from v8
Could you zip up %APPDATA%\McNeel\Rhinoceros and drop it here please and I’ll investigate this error. This is a confidential link that sends it to me and won’t the data won’t be shared with anyone.
on its way. Weirdly I do have folder 6.0 in there, not sure how it got there.
Hi Callum,
Language isn’t a factor for us. All 4 locations use English Rhino installations. I will test the OptionsExporter command when I get that far in my preparations.
Thanks,
Dan
1 Like
I would like to test PreviousOptionsImporter but I get the same error as @vano_artful
