1 What is the maximum number of characters allowed in a
Pro/ENGINEER object name?
Thirty one (31) characters can be used in Pro/ENGINEER
object names. This number does not include the extension, i.e., .prt, .asm,
.drw, or the object version number, i.e., .1, .2, .3.
2 .Can upper case characters be used in Pro/ENGINEER object
names?
Upper case characters cannot be specified in Pro/ENGINEER
object file names. Upper case characters can be specified during object
creation, however, the file will be written to disk using lower case characters
only.
3 what is the reason for using a config.pro file?
The config.pro file is used to control the environment in
which Pro/ENGINEER runs. There are over 150 available options which allow
control of a variety of different aspects, ranging from model display to
default units to search paths used to retrieve assembly components.
4 is a default config.pro file created when Pro/ENGINEER is
installed?
When Pro/ENGINEER is initially installed, there is no
default config.pro file that is created automatically. However, a large number
of the options do have default values which are used unless the option setting
is changed in a config.pro file. The Configuration Options section of Pro/HELP
lists the default config.pro option values in italics. There are two methods
that can be used to create a config.pro file. The first method is to utilize
any text editor, vi for example, and manually create the file. Each option
should have its own line in the file, with the format being {Option Value}. The
second method is to use the Preferences dialog box within Pro/ENGINEER, which
can be accessed by selecting Utilities, Preferences... When you exit the dialog
box, the config.pro file will be written to your local directory. See the
Suggested Technique for Using the Preferences Dialog Box for a detailed
description of the functionality for this new dialog.
5 Where does Pro/ENGINEER look for config.pro files?
Pro/ENGINEER looks for config.pro files in 3 different
directories in the following order:
1) load point/text
Config.pro files residing in load point/text will be read
first.
2) The user's home directory
With UNIX systems, Pro/ENGINEER will read the config.pro
file in the user's home directory. This is most commonly used for specifying
user customized config.pro options such as colors and mapkeys.
3) Working directory
The directory in which Pro/ENGINEER starts is searched for a
config.pro file.
If the same option appears in more than one config.pro file,
the one that was read last will be utilized by the system.
6 After config.pro is edited, why aren't the changes
reflected?
After config.pro is edited, the Add/Change and Apply buttons
must be selected in the Preferences dialog box in order for the modifications
to be reflected in the Pro/ENGINEER session, or Pro/ENGINEER can be restarted.
Be aware that some config.pro options require Pro/ENGINEER to be restarted in
order for config.pro modifications to be reflected.
7 After config.pro is edited, is it necessary to restart
Pro/ENGINEER?
After config.pro is edited, the Apply button must be
selected in the Preferences dialog in order for the modifications to be
reflected in the Pro/ENGINEER session, or Pro/ENGINEER can be restarted.
Modifications to the following config.pro options require Pro/ENGINEER to be
restarted.
8 what is the difference between config.pro and config.sup?
There are two main differences between config.pro and
config.sup.
Unlike config.pro, config.sup can only be located in the
load point/text directory.
Config.sup options cannot be overridden by options found in
any other config.pro. Also, items contained in the config.sup can only have one
entry per option. Keeping this in mind, it is important that items which can
have multiple entries, such as "mapkey", "search path", and
"def_layer" are not specified in config.sup.