Skip to main content
H
hullk1-Visitor
1-Visitor
August 4, 2017
Question

Automatically Saving Config Options Instead of Exporting Configurations

  • August 4, 2017
  • 3 replies
  • 5787 views

Hi,

I am a new Creo Parametric 3.0 user. First things first, I tried to change some options: background color, model display, etc.

 

The issue is that my options are not automatically saved. I find that the only way I can retain my changes is to Export Configurations to the config.pro file in the working directory.

 

This seems a little tedious having to Export Configurations every time I want to keep my options, especially if I forget to do so when I close out of the program.

 

Please help!

 

Thanks,

Kevin

3 replies

D
dschenken1-Visitor
1-Visitor
August 4, 2017

What's the ratio for users wanting to automatically retain changes for the next session but can't remember to save them and those wanting the changes reset to that one-off changes aren't a problem next time.

 

Maybe yet another config option that controls whether config options are automatically saved?

 

You don't have to wait to export, just do it right when you make the change.

 

Helpful hint. config.pro is only a name for an automatically loaded file, and it has to be in the working directory to be automatically loaded (in addition to the one in the install directory, which ought to be more of a site configuration.) You can call the file by any name and manually load it. This means being able to have particular configuration sets for particular projects as well as for special uses, like storing mapkeys. Since it can be any name, using the .txt suffix is really handy as then you can use Notepad or some other text editor by double clicking on the file. A text editor allows removing garbage and organizing to make sure only the config options that are needed are in there. You can also add config options by typing them in and then loading the file in the config editor. Creating a mapkey to load a file, in the file, is handy.

    L
    llie17-Peridot
    17-Peridot
    August 4, 2017

    Please mark Ben's reply as correct

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    August 4, 2017

    Create a config.pro file in your start-in folder. Be sure it is config.pro, not config.pro.txt! You may need to turn on known file extensions to verify this.

    Put in this file any of your configuration options, background color, font, tolerance scheme, etc.

    This file will load automatically when you start Creo.

    If you make changes with in Creo, write the changes to this file everytime you make a change to keep it up to date.

    H
    hullk1-VisitorAuthor
    1-Visitor
    August 4, 2017

    Thanks, but I have a .pro extension and I am able to export configurations (options) to this file for the next session. I just wish not to manually save the config file for every option change, but rather, have it automatic (which I believe is the default for Solidworks).

    S
    23-Emerald III
    StephenW23-Emerald III
    23-Emerald III
    August 4, 2017

    When I make changes to my options and I click OK, I get a "do you want to save" pop up window.

    Don't use the import/export button..

    When you click YES, it saves your options to the active config.pro.

    If they are not saving, you likely don't have write access to that folder.

     

    options.jpg

    E
    erine1-Visitor
    1-Visitor
    August 16, 2017

    I'm not aware of any way to automatically save your settings without saving to your .pro file.

     

    On a sidenote, your color options are not saved to config.pro.  They are saved to a separate file (default name is "syscol.scl") that is driven by an option in your config.pro file.  THAT option is called "system_colors_file" (which may need to be inserted into your config.pro file, if you've changed your default working directory's location

     

    If your color options are consistent through sessions, disregard this.  It means you are writing to the correct location when saving them. Also, some of the more experienced guys chime in if i'm off base here.

    Terms & ConditionsAccessibility statement