Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.
well, first I am not sure if I understand You right
well, maybe you already wrote that, but... I thinking of the way to have a file for example like this: user__all_mapkey.mpk(extension is just an idea), and push somehow Pro\e to look for extra mapkeys in this file
Why one can ask? Well, it prevents loosing all mapkey with new config. pro release.
What caddie was getting at is that Pro|E looks for 4 config files at startup, in 3 different locations:
<LI>config.sup in the <loadpoint>/text folder. Options in this file cannot be overwritten by other files. Don't put mapkeys in this file as Pro|E will thenonly read one mapkey statement, no more. Config.sup has to be in the <loadpoint>/text folder.</LI>
<LI>config.pro in the <loadpoint>/text folder. </LI>
<LI>config.pro in the user's home directory. This is defined by Windows environment variable %HOME%.</LI>
<LI>config.pro in the startup folder. This is defined by editing the 'start in' field in the shortcut properties for the shortcut icon used to launch Pro|E</LI>
Pro|E loads these files cumulatively, later options overriding earlier ones. So, you could solve both of your issues by having 2 config/pro files outside of the <loadpoint>/text folder. Put your main config.pro in your Home directory and place the mapkeys config in the startup directory. You'll have to use the file name 'config.pro' for each in order for Pro|E to read it.
By removing your config/pro file from the <loadpoint>/text folder, it won't get lost if you upgrade to a newer build.
Another way to do it would be to use a batch file to assemble one config file from several and placing it in one of those locations. You'd then call that batch file first when launching Pro|E. That's a bit more involved, however.
Not sure you would lose all your mapkeys, you just have to keep backups of your important files, and then if neccessary just manually add to the new config.pro when it is issued (?)
well andysuth, this is what I do day by day. It has to better way
caddie - i gonna try that. I am not so young to not know what the hell DOS is, but in fact I am not so familiar with all commands it had, so the sentence c:\a.txt >config.pro sound for me as following: Content from a.txt will be put inside config.pro, am I right?
but this one : if exist d:\config.pro del /Q d:\config.pro is not clear enough still for me
I'm not familiar with DOS programming, but I think that just deletes the existing config.pro, if it exists.
Here, we keep company config.sup & config.pro on the server. A batch file copies the files to the loadpoint at startup. I also copies the appropriate icons to the start menu, asks the user what client they are working in and sets a trail file to load a client config (if one exists) for that client, sets the startup folder and launches Pro|E.
This allows me, as the admin, to change the config file at any time and the users automatically get the new one when they start Pro|E. I hate things that have to be updated manually, if possible I want it automated. Easier and more reliable that way.
muadib3d, I'm now fascinated to know why your Config.pro file would change on a daily basis. surely it's time to have a variant in a local directory and start ProE from that directory.
The "If Exist" checks for the file name, then only tries to delete it if there is something there.
Would you prefer a Macro for MS Office to do this? I've got one quite similar that changes the content of a trailfile to suit the new file names needed to be generated.
I've asked before but I really think the ProE forum should have a dedicated automation forum, and I'll happily post on a fair few macros that I run from MS Office (Outlook or Excel) that automate with ProE.
I have told you how to put different files into a single config.pro file, but in general I have to agree with "dgs" when he/she says:
"Here, we keep company config.sup & config.pro on the server. A batch file copies the files to the loadpoint at startup."
That is the method we use as well. It makes it extremely easy to administer all users (100+) and to make sure all users are updated the next time they start the software if you make a change.
How about you have a batch file that opens ProE from a local directory, and have a local config.pro with your settings and batch files in?
So whilst the ProE is loaded from the network, so long as there are no mapkeys in the config.sup then the mapkeys in the local config.pro (in a local directory) would still be there for you?
Or what about running a trail file to load in your mapkeys?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
