Setting config.

win Options
You can make window configuration changes to Pro/ENGINEER only during an active
session. You can make changes using only the Customize dialog box. Open the
Customize dialog box by clicking Tools > Customize Screen.
As with the config.pro, the config.win file uses a hierarchical approach to
configuration file settings. First, it looks in the loadpoint/text and home directories,
then at the local directory. The settings are reflected as it moves down the hierarchy.
You can retain different window configurations by saving multiple versions of
config.win and loading the desired configuration file during a session, rather than
by changing a single config.win file every time your window configuration needs to
change.
SHOW NAVIGATION << >>

About Configuration Files

You can customize the look and feel of Pro/ENGINEER and the way in which
Pro/ENGINEER runs by setting options in a configuration file. Pro/ENGINEER contains
two important configuration files: config.pro and config.win. The config.pro file
is a text file that stores all of the settings that define the way in which Pro/ENGINEER
handles operations. The config.win file is a database file that stores window
configuration settings, such as toolbar visibility settings and Model Tree location
settings. Each setting in the configuration files is called a configuration option.
Pro/ENGINEER 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

• Toolbar contents

• Relative button order on a toolbar

• Location and size of the Model Tree

Note: 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.

About menu_def.pro
The menu_def.pro file is a configuration file that controls the look and feel of the
Menu Manager. Typically, your company system administrator would set up this file
in order to customize the Menu Manager according to the needs of your workgroup.
You can also create your own menu_def.pro file and further customize the Menu
Manager locally.
How Pro/ENGINEER Reads Configuration Files at Startup
Pro/ENGINEER reads configuration files automatically from several areas. If a
particular option is present in more than one configuration file, Pro/ENGINEER
applies the most recently loaded/read setting.
At startup, Pro/ENGINEER 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. loadpoint/text (loadpoint is the Pro/ENGINEER 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 Pro/ENGINEER 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 Pro/ENGINEER from any directory without
having a copy of the files in each directory.

3. Startup directory − This is your current or working directory when you start
Pro/ENGINEER.

Note: 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.

See Also
About config.pro Options
To Save config.win Changes Automatically
To Load a config.win File
To Set config.pro Options
To Search for a Configuration Option