it would be nice, but maybe not today?
I can’t imagine I would have to start over with this
Any thoughts on this?
Thx,
G
It’s been about a year already since the first mention.
I can’t imagine this being something really complicated?..
I just want my color scheme back…
Really? Can you tell me more about why this is your main roadblock?
^ Because we have so many custom settings, starting with UI colors and ending with custom display modes that plugging it all in manually is too dam long. And still in the end something will be left overlooked.
If anything, let us import Display Modes and Appearance.
too many options that makes my Rhino work the way I’m used to. and too little time to do them form scratch.
rhinoV5_options_gus_161019.zip (17.7 KB)
also I want to brig all these…
maybe I should stop bitching a recreate all the options from scratch, import each vieew mode one-by-one, ugh?
@gustojunk, are these .ini files just display modes? If so, then you can import them using just Rhino (Tools > Options > Views > Display Modes > Import). RhinoScript has a method to import display modes, so you could write a script to import them all a once (too).
– D
those are separate that all the applications options I had. the biggest hurdle was aliases. But I just realized I can export from the Aliases page a text file and import in V6!
Dang, I didn’t realize there was Export option for Display Modes… That makes it easy…ier.
When I try to import an .ini file to V6 that’s the message I get.
Quiet a nonsense.
If someone can help.
version :
Work In Progress
(6.0.17129.11351, 09/05/2017)
Beta
Hi Borix - please post the ini file here or to tech@mcneel.com, someone will take a look.
thanks,
-Pascal
I had the same problem. Looks like the dialog has a bug with the file path.
As a workaround you can use the scripted version of the command
-_OptionsImport and feed in the full path to your ini file.
Edit: If there are spaces in your path then surround it by quotes:
_-OptionsImport “C:\My Options\test.ini”
thank you Jess