About Configuration Files
You can customize the look and feel of Creo Parametric and the way in which Creo Parametric runs by setting options in a configuration file. Creo Parametric contains two important configuration files: config.pro and files with .ui extension. The config.pro file is a text file that stores all of the settings that define the way in which Creo Parametric handles operations. Each setting in the configuration files is called a configuration option. Creo Parametric provides default values for each option. You can set or change the configuration options. Some of the options you can set are:
• Tolerance display formats
• Calculation accuracy
• The number of digits used in sketcher dimensions
A file with .ui extension is a text file that automatically stores any change that the user does in the customization. It stores ribbon customization, window settings, and many other settings
Config.sup is a protected system configuration file. Your company system administrator uses this file to set configuration options that are used on a company-wide basis. Any values that are set in this file cannot be overridden by other (more local) config.pro files.
When an option is locked using config.sup file, the option becomes unavailable and a lock icon appears next to the option. The config option is used to lock options on the Options dialog box, Quick Access toolbar, Graphics toolbar, and anywhere on the ribbon user interface. For example, if the datum display filters are locked, the control is disabled and a lock is shown on the Options dialog box, in Entity Display tab, under Datum display settings.
The datum display filters are also locked in the Configuration Editor , View tab, and on the Graphics toolbar.
How Creo Parametric Reads Configuration Files at Startup
Creo Parametric reads configuration files automatically from several areas. If a particular option is present in more than one configuration file, Creo Parametric applies the most recently loaded/read setting.
At startup, Creo Parametric first reads in a protected system configuration file called config.sup. It then searches for and reads in configuration files (config.pro, config.win, menu_def.pro) from the following directories in the following order:
1. <creo_loadpoint>\<version>\Common Files\text (creo_loadpoint is the Creo Parametric installation directory) - Your system administrator may have put configuration files in this location to support company standards for windows configuration settings, formats and libraries. Any user starting Creo Parametric from this loadpoint uses the values in this file.
2. Login directory—This is the home directory for your login ID. Placing your configuration files here lets you start Creo Parametric from any directory without having a copy of the files in each directory.
3. Alternate Path—You can set the environment variable PTC_CREO_ALT_SETTINGS_PATH to point to an alternative path where you store your configuration files. This path could be set to any mapped network drive or a shared OneDrive folder.
The following files are read automatically from the directory that PTC_CREO_ALT_SETTINGS_PATH points to:
◦ config.pro
◦ config.sup
◦ creo_parametric_admin_customization.ui
◦ creotk.dat/protk.dat/prodev.dat
You can create sub folders in this alternate location to store company specific custom formats for the following:
Folder | Corresponding Configuration Options |
---|
templates | start_model_dir |
notes | pro_note_dir |
graphic-library | graphics_library_dir |
symbols | pro_symbol_dir |
custom hole parameter files | hole_parameter_file_path |
simulation templates | simulation_process_template_dir, sim_pp_template_dir etc. |
4. Startup directory - This is your current or working directory when you start Creo Parametric.
| The local configuration files (config.pro, config.win, and menu_def.pro) in your startup directory are the last to be read; therefore, they override any conflicting configuration file option entries. The config.pro file does not, however, override any config.sup entries. |
You can create and store custom configuration files in your current working directory. These custom configuration files usually apply to specific projects. This path is the last to be read and takes precedence over all other paths and overrides all other config.pro and config.sup settings.