Skip to main content
1-Visitor
May 22, 2012
Solved

How do you save and keep Option settings in Creo?

  • May 22, 2012
  • 3 replies
  • 84141 views

I am a new user of Creo. There are some settings that I wish to save and keep, but I'm not sure how this should be done.

In Environment Options there is a place to save Working Directory. I have tried on different occasions to save a different location for my Working Directory, what is the trick to getting this to stick? It stays until you get out of Creo.

Also I would like to modify some of the Config.Pro options. When this gets saved where should it be saved to? There doesn't appear to be a logical place to save this.

Best answer by BrianMartin

The config.pro file can be located in any one (or ALL) of three locations:

  • Creo loadpoint
  • User's "Home" Profile Directory
  • User's Working Directory

The LAST FILE READ always wins. So, for example, if you had a config.pro file in your home directory setting your grid to "ON" and another config.pro file in your working directory setting the grid to "OFF", the working directory wins.

The easiest and safest place to put your config.pro is in your working directory. If you have multiple directories you work from, you may want to put your file in the "Home" directory instead. For XP users this is typically "c:\documents and settings\<your user name>\my documents". For Windows 7 users this is something like "c:\users\<your user name>\documents". Your home directory may be different. If you need help finding it, I can give you better instructions to locate it.

Thanks!

-Brian

3 replies

1-Visitor
May 22, 2012

hello,

To change your startup directory you have to right click on the Creo Parametric shortcut on your desktop and choose Properties, then change the path in Start in Field to whichever you want.

If you keep your config.pro file in that directory it will load automatically when you run Creo using this shortcut.

dellens1-VisitorAuthor
1-Visitor
May 23, 2012

I appreciate both of your replies.

I have modified the shortcut as suggested. Creo doesn't automatically load up in the modified directory but if I click on Working Directory it does take you directly to the changed start in location. This is fine, but if it could automatically load in the modified start in location it would be even better. I don't know if this is possible?

I changed my Start In: to C:\PTCU because our training resides in this folder. In reading the above.

If you keep your config.pro file in that directory it will load automatically when you run Creo using this shortcut.

I am to understand that I would need to save my config.pro modifications to the C:\PTCU folder? In other words I should save my config.pro modifications to the Working Directory?

13-Aquamarine
May 23, 2012

The config.pro file can be located in any one (or ALL) of three locations:

  • Creo loadpoint
  • User's "Home" Profile Directory
  • User's Working Directory

The LAST FILE READ always wins. So, for example, if you had a config.pro file in your home directory setting your grid to "ON" and another config.pro file in your working directory setting the grid to "OFF", the working directory wins.

The easiest and safest place to put your config.pro is in your working directory. If you have multiple directories you work from, you may want to put your file in the "Home" directory instead. For XP users this is typically "c:\documents and settings\<your user name>\my documents". For Windows 7 users this is something like "c:\users\<your user name>\documents". Your home directory may be different. If you need help finding it, I can give you better instructions to locate it.

Thanks!

-Brian

13-Aquamarine
May 22, 2012

Jakub is correct...

Your working directory by default is whatever directory Creo starts in. If you use a shortcut to launch Creo, you can set that "Start In" directory in the shortcut properties as Jakub stated. Also, if you go down into the Creo loadpoint (where all the files for the software are stored), down inside the /bin directory, you can add commands to the startup batch files to set your working directory. This is a bit more advanced but if you need help doing this, write back. Jakub's solution will probably be the easiest for you to implement.

Thanks!

-Brian

12-Amethyst
January 25, 2019

I'm trying to coach a new user in CP4 configuration settings and the CP4 configuration editor has me befuddled.  Where Creo reads configuration files has been asked an answered.  Creating a new configuration file is fuzzy.

 

In our installation, load point and start-in locations are controlled by the sysadmin.  So the next logical place for personal options is %HOMEDRIVE%%HOMEPATH%\config.pro.

 

Since he's a new user, he doesn't have any configuration files here.  I can brute-force it the pre-Wildfire way with Notepad, but I have a hard time believing that's the CP4 "recommended" way.

 

Example: He doesn't read his message area. To solve a pain point for me, I want him to have 3-5 lines show up in the message area.

Expected outcome: From the Configuration Editor, create new config.pro file in the %HOMEDRIVE%%HOMEPATH% folder, containing the visible_message_lines and the desired value.

 

Undesirable outcome: duplicating any option from "all options", "current session" loadpoint, start-in, etc. into the %HOMEDRIVE%%HOMEPATH%\config.pro.  Why? If the sysadmins change an option in the loadpoint or start-in locations, the leftover garbage in the personal config.pro.  (Let's not bring up a config.sup discussion - not helpful for this question.)

 

Undesirable outcome: Saving the property in the loadpoint or start-in config.pro.  Why? Overwritten by sysadmins.

16-Pearl
January 30, 2019

@akelly wrote:

Since he's a new user, he doesn't have any configuration files here.  I can brute-force it the pre-Wildfire way with Notepad, but I have a hard time believing that's the CP4 "recommended" way.

 


I see nothing wrong with this approach, as long as you know correct option names and their values. Config.pro is a text file, it doesn't matter what method you used to create it.

 


Example: He doesn't read his message area. To solve a pain point for me, I want him to have 3-5 lines show up in the message area.


Expected outcome: From the Configuration Editor, create new config.pro file in the %HOMEDRIVE%%HOMEPATH% folder, containing the visible_message_lines and the desired value.

 

Undesirable outcome: duplicating any option from "all options", "current session" loadpoint, start-in, etc. into the %HOMEDRIVE%%HOMEPATH%\config.pro.  Why? If the sysadmins change an option in the loadpoint or start-in locations, the leftover garbage in the personal config.pro.  (Let's not bring up a config.sup discussion - not helpful for this question.)

 

Undesirable outcome: Saving the property in the loadpoint or start-in config.pro.  Why? Overwritten by sysadmins.


In Creo options are exported with regard to filter set in upper right corner, as you can see here:

2019-01-30 09_27_39-Window.png

 

If you want to export only newly added options and not all the options read to current session, simply change this Show filter to Only changed and then export configuration to config.pro. It should contain only the options you added (or modified) in current session, not all the options loaded into session.

12-Amethyst
April 10, 2019

Hi,

 

I'm still lost with all this...  any & all help is much appreciated!

 

I want to customize my Creo to a few things I want, that differ from the department.  I have a created a number of Config.pro files, but none seem to get read, no matter where they're put.  It would seem the last read config.pro is the one that I don't want to change, as it's the company standard one.

 

I cannot change the "start in" in the short cut as:

- it's administrator controlled (needs a password - but ther is a work-around of makigna copy of eth short cut, and making eh change there..)

- and if changed, I'll then need to re-set my 'working directory' each & every time I start my day.

 

Surely there's an easy way to have a personalized config.pro...  Or, are we not set up right, as we're looking in the start in directory for the company standards..  (And should be using a config.sup file..)