Configuration Files

The configuration files of Pro/Engineer include config.pro, config.win, and menu_def.pro. The config.pro file is a text file used to store the optional settings for the operation handling of the Pro/Engineer. The config.win file is a file used to store the settings of window configuration, i.e. toolbar and model tree settings. The menu_def.pro file is a text file used to store the settings of the menu manager. Each optional configuration setting has a default value for each configuration option.

 There can be more than one copy of these configuration files which are stored in different directories for the system to load during startup. The reading sequence of the configuration files is config.pro, config.win, and menu_def.pro.  These configuration files are loaded from different directories in the same order. The order of directories in which these configuration files readed from is the loadpoint directory (the intallation directory of Pro/Engineer), the login directory (the home directory of the login user), and the startup directory (the  startup working directory of Pro/Engineer). In general, the optional settings of the configuration options are cumulative and the existing configuration settings can be overwritten by the most recently loaded setting read from the configuration files.

Config.pro

Config.pro is a configuration file of Pro/Engineer. Pro/Engineer uses configuration files to define the default setting of the Pro/Engineer. The configuration file options or the setting of the Pro/Engineer can be modified session to session.

During the startup of Pro/Engineer, Pro/Engineer retrieves config.pro files from serveral directories. The rule of handling the option is  reads   if a particular option is present in more than one configuration, Pro/Engineer applies the most recently loaded/read setting.

At startup, Pro/Engineer first reads in a protected system configuration file called config.sup.  The  config.sup have the same options as the config.pro. The configuration file have the extension "sup" because this is always the first configuration file loaded by Pro/Engineer and the option settings of the config.sup cannot be overridden by other confilg.pro files read after the config.sup. The config.sup is usually to hold the standard settings that are used as the grobal preset standard and are not to be modified by using local config.pro files. The location of the config.sup is in the text subdirectory of the Pro/engineer loadpoint. Then the system will look for the config.pro file at the same subdirectory. The config.pro is usually to hold the standard settings that are used as the grobal preset standard for all users and are to be modified by local user settings using local config.pro files in login directory.

Then the system will looks in the home directory of the login for a config.pro file. This local user config.pro is usually to hold the standard settings that are used as the grobal preset standard for the local user and are to be modified by local user project settings using local project config.pro files in project working directory.

Finally, the system will looks in the startup in or working directory for a config.pro file.  This local project config.pro is usually to hold the standard settings that are used as the grobal preset standard for the local project and are to be modified by manual settings using the "Tools/Options" menu command.

During a session, the options setting of the Pro/Engineer can also be modified and overwritten by loading a specific config.pro file through "Tools/Options" menu manually.

But local user can, among other options set in config.sup file, set their own option settings.