Making mapkeys always active Wildfire 3.0
Making mapkeys always active Wildfire 3.0
(OP)
I am trying to set up mapkeys to reduce some of the redundant menu commands that I do in Wildfire 3.0. The mapkeys only work for the current session.
Does anyone know how to make them always work?
Thanks
Does anyone know how to make them always work?
Thanks





RE: Making mapkeys always active Wildfire 3.0
After making your selection, you will be promped to pick a name for a congig file. What I do is change directories and select the last config file that is run when I start pro/e. There are a number of locations that config files are located in, you may want to do a search in this forum or the Pro/E help for more information on config files.
Peter Stockhausen
Pollak Switching Products
RE: Making mapkeys always active Wildfire 3.0
If you ever run into the case where you have to rename a mapkey open the allmapkey file in a text editor and search for "key_sequence @M"
If I had a mapkey with sequence
[b]lcs[b] for [b]Layer Create Surfs[b] and wanted a mapkey to create a solid layer I could search for [b]lcs @M[b] and rename lcs lcsu and delete the lcs mapkey then use lcso for the Solid Layer mapkey.
Pro/E disables you from renaming the sequence from the Modify option in the Mapkey dialog although you could rename in Options if you choose to keep your mapkeys in the config file and use save changed.
Michael
Peter, do you work at Pollak in MA or somewhere else?
Just Wondering
RE: Making mapkeys always active Wildfire 3.0
Peter Stockhausen
Pollak Switching Products
RE: Making mapkeys always active Wildfire 3.0
I setup a mapkey "dist" to measure distances and i moved the text file
"config.pro" into a directory. I then closed pro engineer and reopened it set the directory with the config.pro file in it as the working directory. However now when I hit the key board shortcut that I assigned for measuring i don't get a response.
Can someone tell me what to do?
RE: Making mapkeys always active Wildfire 3.0
"I'm only running Pro/E 2001 but here is some information from the help files.
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 current 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 and config.win) 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.
Notes: The local config.pro and config.win files (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.
Heckler
Sr. Mechanical Engineer"
You need to make sure the config files are in the correct directories.
Peter Stockhausen
Pollak Switching Products