Mapkey Storage Preferences

[JakeAdkins]

Does anyone know where mapkeys are stored in Pro/E?

I launch Pro/E from Pro/Intralink off our network. We have a standard config file that loads so we all have the same set up. I wrote some mapkeys and they worked fine until I closed Pro/E. When I wrote the keys I saved my config file on my C: drive, but when the keys don't work when I load that config file.

That leads me to believe that the mapkeys are not stored in the config file. How can I get these mapkeys to load each time so I don't have to re-map them each time?

 

[fighterpilot]

I store mapkeys in the config.pro file. However, there are typically three config.pro files.

1. <loadpoint>\text\config.sup
2. <loadpoint>\text\config.pro
3. <user working directory>\config.pro

Don't put any mapkey statements in the config.sup file. If you do, no one will be able to create their own personal mapkeys. Pro/E looks at this config file first upon startup.

Put corporate standard mapkeys in the config.pro, item 2. Pro/E looks at this file second upon startup. Finally the user should put their personal mapkeys in the config.pro as in item 3. Pro/E looks here last.

Mapkey definitions listed in item 2 can be overwritten by those same keys in item 3 if necessary. However, if ANY mapkeys are defined in item 1 then none can be defined later.


--
Fighter Pilot
Manufacturing Engineer

 

[jeff4136]

Pro/E looks three places for config.pro files and loads
any it finds. See...
Help
.Fundamentals
..Pro/Engineer Menus
...The Tools Menu
....Using Configuration Files
.....How Pro/Engineer Reads Configuration Files at Startup

You can put your mapkeys in any of them. Particulars
will depend on how you launch Pro/E and desired effect.

You can also store them in one or more discrete files,
i.e. my_mapkeys.pro, and manually load (Tools -> Options).

(
My preferences:
When creating a new mapkey I save it to a discrete file, then cut and
paste to config.pro. I don't want the mapkey editor writing to my
config.pro.

The majority of mapkeys reside in my 'primary' config.pro;
homedrive\hompath\config.pro. (I don't have one in \loadpoint\text\.)

I usually set up a 'project specific' config.pro in the project
root directory with search path statements, non-standard option
settings and, maybe, nonstandard mapkeys. I launch Pro/E from
the project root via Windows Explorer RMB shortcut so this config.pro
is the last read.

Rarely used mapkeys are kept in their discrete files and loaded manually.
)


-Jeff Howard (wf2)
Sure it's true. I saw it on the internet.

 

[looslib]

Well, it actually looks in 4 places! You missed the Start In directory on windows machines. We also use a fifth file at startup by running a mapkey on the startup line which loads the program specific settings.

The order is:
<loadpoint>config.sup - values can NOT be changed
<loadpoint>config.pro
$home\config.pro
<Start in>config.pro
Mapkey loaded at startup


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli