How to save settings? Very confusing!

Working on new Rhino courses – AND – ran into an issue. I was hoping to save my keyboard shortcuts / settings, but it looks like that command was in older versions and omitted from Rhino 8.

I then got into a long discussion with ChatGPT about the following commands, but none worked for me:
_ImportOptions and _ExportOptions
ImportOptions and Export Options

I was also looking to get a way to save the interface / toolbars, but that is also a separate command using .rui.

ChatGPT said that these (five?) commands to save settings have not been changed / consolidated to avoid breaking backwards compatibility.

QUESTION > Could you create onw brand new ‘uber-command’ that saves all customizations?

Ideally, it would have a checkbox for ‘just keyboard shortcuts’ or ‘just display modes’ or ‘everything, baby!’

2 Likes

OptionsExport and OptionsImport should still work for aliases and keyboard shortcuts:

Thanks! This will hopefully work. I will have to test it out.

Is _ExportOptions, ExportOptions, and (what you wrote) OptionsExport three unique comands?

This is part of my confusion.

OptionsExport is the current command. I’m not sure if ExportOptions was used previously, but it’s not now. As I understand, adding the underscore just forces Rhino to look for English-language commands, so users with other languages as default can still copy/paste the underscore versions and have them work.

3 Likes

Can anyone confirm the file type that is created? Is it an .ini?

Yes .ini

1 Like

Dave,
I don’t know why you are “discussing” this kind of stuff with ChatGPT - it doesn’t know crap about Rhino, it’s only vaccuming up the (mis)information that people have posted on various places on the internet and spitting it back at you.

As Gijs said, OptionsExport and OptionsImport exist since V5 still work in V8.

In V8, if you would like to transfer all of your settings - including toolbars, etc. the easiest way is to simply copy the entire ‘settings’ folder from one computer to another. This is valid as long as you haven’t made an external .rui for your custom toolbars. If you have an external .rui, you need to back that up separately. There are several threads on this. You can even ask ChatGPT if it knows anything about it…

You might want to check out the following as well:

1 Like

Thanks for all of the help! So, here is an update. Two issues:

ISSUE 1 > When using OptionsExport (to create an .ini file) I have a 25 to 30 second delay. This is why I cancelled it the first try, thinking it failed. File size is 232 KB.

ISSUE 2 > [On Export] I do not get the dialog for choosing options. I assume it is exporting everything.

When I run OptionsImport, then I do get the dialog.

QUESTION 1 : Can you confirm the above is expected behaviour?
QUESTION 2 : Why does the Export take so long?

Very good points and you are 100% right about ChatGPT. However, I did not know the exact name of the command AND had never used it, so it was confusing seeing older commands pop up in my research, whether in Help / Online / ChatGPT. :slight_smile:

The new system seems fantastic. Well done!

I need to remember not to kill the Export process when it appears to hang and the titlebar says ‘Not Responding.’ That has happened in every test.

Hi Dave -

Yes.

Because it uses WritePrivateProfileString, perhaps?
I’ve added this thread to RH-67579 OptionsExport takes a long time when saving to network location
-wim

Another good observation. All of my tests were local. This is odd! The file is tiny (232 KB) and the writing is local, so I guess there are a lot of disparate options to assemble.

I just checked the option.ini file with notepad. It has 5,195 lines of data. That’s got to be part of the equation. That’s a hella load of options!

QUESTION > Is this a function that would benefit from a progress bar?

Hi Dave -

Yes, a comment in RH-67579 states that this is not strictly a network issue.

This function would benefit a fix for RH-67579.
-wim

I just read the ‘YouTrack.’ This is why the Rhino team is the best! Thanks again.

Instead of adding [solved] to the topic title, could you maybe mark a post as solution?

Good idea. Fixed it.

1 Like