Load configs from config.pro

[Zestje]

Hello,

Is it possible to load additional config files from a config.pro
something like a 'load' command, e.g.:

load X:\path\mapkeys.pro

I would like to have a separate config file just for own mapkeys that I use in every project.
I prefer not to use config files in the ProE program directories, because I want to have all my configs for all different projects in the same place (in separate subfolders for each project). This way it's easier to port my configs to other computers, because all I have to do is copy my config folder to the other PC, create a new shortcut and set 1 parameter in windows to that config folder.

Having just 1 file for my standard mapkeys is easier to handle and update and also prevents problems with different config.pro setting that different clients require.

Thank you for your help

 

[looslib]

You can load config.pro from 3 locations in Windows in this order:


1. <proe_loadpoint>/text. Used for company settings. Also the config.sup is loaded from this directory.


2. Login/Home directory - Windows environment variable: Home. This is where you should put your personal config.pro.


3. Startup directory - defined in the icon shortcut. If you have multiple projects with their own configurations, create multiple icons on your desktop for each project.


Settings in the last config.pro loaded will overwrite earlier file reads.


There is one other method and that involves running a mapkey at startup which reads a config.pro. We use this for drawing formas, start parts and templates as our engineers move between programs.

 

[Zestje]

@looslib

Thank you for your answer, but it is not really what I meant.
The method that loads a config using a mapkey should work, but it's not a very nice method.

I know the methods to load configs on startup, but I would like to know
if it is possible te execute a config file from within another
config.pro.

Is there a way to do that?

 

[looslib]

Not that I am aware of, which is why I listed the known methods.

 

[jnoval]

You can make a proE start command to run a trail file after startup. You can perhaps load the config.pro file from the trail file.


Perhaps you can use this. This will require different start commands for different projects. If I have understand you correct.

 

[looslib]

The mapkey is run automatically from the line that starts the Pro/E process. We have an environment variable set depending on user's project and when they satrt Pro/E, it runs the appropriate mapkey which sets the start parts, formats and templates for that project.