9 Is there a limitation on the number of characters that can
be included in a config.pro entry?
Ans: Each line in config.pro is limited to 80 characters.
Environment variables can be used to specify config.pro "search_path"
values containing more than 80 characters. Refer to Configuration Options in
Pro/HELP for details.
10 Where are Pro/ENGINEER objects stored when File, Save is
selected?
By default, Pro/ENGINEER objects will be stored to the
current working directory. If the working directory is changed using File,
Working Directory, Pro/ENGINEER objects will be saved to the new directory. If
a Pro/ENGINEER object is retrieved from a directory other than the current
working directory, Pro/ENGINEER will save the object back to the directory from
which it was retrieved. If the user does not have write permission in that
directory, the object will not be saved unless the config.pro option "save_object_in_current"
is set to "yes".
11 What does File Save As do?
File - Save As will make a copy of a specified Pro/ENGINEER
object using a new name. List the object that is to be copied in the Model Name
space in the Save As dialog box, the current object being the default. In the
New Name space, a new file name should be specified. Pro/ENGINEER will create
this object in the current working directory.
12. what does File, Backup do?
File, Backup can be used to save Pro/ENGINEER objects to a
specified directory. The object will be saved in the specified directory using
the original filename(s).
File, Backup in Assembly, Drawing, or Manufacturing modes
will save all related objects to the specified directory.
13 what does File, Rename do?
File, Rename is used to change the name of Pro/ENGINEER
objects in memory and on disk. Pro/ENGINEER will rename all versions of the
object being renamed.
When renaming an object that was retrieved from directory
other than the current working directory, the renamed object will be saved in
the directory from which the object was retrieved.
14 what does File, Erase, Current do?
File, Erase is used to clear the specified object from
workstation memory. This functionality will not remove objects from disk. Objects
referenced by an active assembly or drawing can not be erased. A list of
objects in the current model will then be displayed. Only the current top level
model (i.e. assembly or drawing) can be erased, and selected objects as well.
15 what does File, Erase, Not Displayed do?
Ans: File, Erase, Not Displayed is used to erase all objects
from the current session, except for those that are currently displayed and any
objects referenced by the displayed objects. For example, if an assembly
instance is being displayed at the time Erase, Not Displayed is selected, the
instance, the instance's generic, and it's components will not be erased. There
is a config.pro option related to File, Erase, Not Displayed called
"prompt_on_erasenotdisp".
yes (default) - a message window for each eligible object in
question appears, asking if you want to first save the object before it is
erased.
no - the system will immediately erase all eligible objects.
16 What does File, Instance Operations do?
File, Instance Operations will save a particular instance of
a part or assembly in a separate file called an " instance accelerator
file" (suffix ".xpr" for a part, ".xas" for an
assembly). This file is used to retrieve particular instances quickly from disk
rather than having to first retrieve the generic into memory, selecting the
particular instance according to the family table, and then regenerating.
Therefore, with this functionality the amount of time that it takes to retrieve
an instance of a part or assembly from disk can be considerably reduced. The
trade off is that more disk space will be used to store the accelerator files.
When File, Instance Operations is selected, the INST DBMS menu appears with the
following options
InstIndex - create or update the Instance Index file for a
specified directory
pdate Accel - create or update accelerator files for all
instances currently in session
Purge Accel - examine each instance accelerator file and
delete it if it is not current with
SaveAccelEnv - brings up the SV INST ACC menu When
SaveAccelEnv is selected the SV INST ACC menu appears with the following
options:
none (default) - the system does not save the instance in a
file separate from the model.
always - the system always saves the instance in a separate
file
explicit - the system saves the instance in a separate file
only. When the instance is explicitly saved.
The config.pro option "save_instance_accelerator"
can also be used to control instance accelerator files. The values for this
config.pro option are also none (default), always, explicit. When you bring up
the SV INST ACC menu, one of the options will be highlighted to reflect the
last setting. That setting could have been either loaded from a configuration
file or selected previously from this menu.