Trail files
Pro/E creates a 'trail file' every time it is run. This records each action the user takes.
Trail files can be useful for 'replaying' actions when Pro/E crashes, for example:
- Rename the latest trail file (usually created in the startup folder) & remove the .1, .2 suffix
(Note: don't call the file trail.txt - this name doesn't work)
- Open the file in a text editor and remove the last few lines. You will be able to see where the different commands were called - pick an appropriate stopping point.
- Use Tools - Play Trail/Training File... and select the edited text file.
Trail files may also be used for automation or demonstrations - ie to rerun a common feature or series of commands (useful in some instances where mapkeys are not effective, like recording spinning and screen picks, etc)
- When recording the trail file, watch your references - try to use 'Sel by Menu' for picking datums, etc.
- Minimise spinning, panning & zooming where not necessary.
- Occasionally set the model to Default View to recalibrate the view.
- Edit the text file created - remove the last few lines which exit Pro/E.
- If you are creating a trail file for a demo, don't save - this will leave the models in the same state for the next demo...
A couple of handy config.pro options for trail files:
- trail_dir - the folder where trail files are stored (defaults to working folder)
eg: trail_dir c:\ptc\trails
- trail_delay - this sets the delay between steps
eg: trail_delay 3 for a 3 sec delay
- set_trail_single_step yes - this makes Pro/E wait for you to press Enter before performing the next command.
Example of trail file use: you could save some trail files that create basic features (extrude & revolve) using default datums in the start parts as references.
Then add a mapkey which selects "Play Trail File" & navigates to the trail text folder - ready to run.
Updated 8-Feb-06
