Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
I'm new to the software and made the mistake of saving "All" everytime I made a new mapkey. I now have a config file that is 177,026 lines long.
I've tried opening it up in a text editor and working on it but the way it's written out the file is very difficult to manage.
Is there a trick, tip, or tool to help clean this mess I've gotten myself in?
Thanks in advance.
(I did a search but some of them were a little out of date or didn't address the possibilty of a tool or method to help.)
Solved! Go to Solution.
Maybe try to load it in Pro/E or Creo and then export it from there into a new file.
Maybe try to load it in Pro/E or Creo and then export it from there into a new file.
You sparked a lightbulb for me. I see I can saved the currently loaded options to a seperate file. That'll make my job a little easier.
Hi
If you go to Olaf Cortens web site (ProESite - Olaf Corten's Pro/ENGINEER Site - Pro/E Utilities, Benchmark, Tips and Links) he has an on line tool that will detect any duplicates or any flaws in your config.pro and covers versions from PROE R20 up to CREO 3
We also have some comment markers in our Config files to show which are the config.pro and config.sup that are pushed to the text folder. Won't help for all the duplicates but it should help eliminate some of the extras.