Config.win path

[Asho Pulsar]

Hi,


Can someone tell me that where exact location to be set and save the config.win so that modified toolbar locations has to be same place when i open the proe again.


Thnx in adv.

 

[robertib]

If you right-click on the icon you use to open Pro/E & select Properties, you will see an option forstartup directory - this is where you should put your config.win, config.pro, tree.cfg, etc files (or change the startup directory to where you store the files).

 

[Asho Pulsar]

Thanks robertib,


It worked out, but i dont think that config.pro also to be saved in the startup directory. It can bestored in different location right!!!

 

[Guest]

Configuration files are read from several places. If there is a config.pro file in the startup directory this file is read last and overrides any conflicting options previously loaded except those loaded from the config.sup. You can put config.pro in working directories and load them once you have started ProE.


Configurationfiles are read from the installation directory for ProE in the text folder. Another location for the files is your login directory on your computer.

 

[Asho Pulsar]

Configuration files are read from several places. If there is a config.pro file in the startup directory this file is read last and overrides any conflicting options previously loaded except those loaded from the config.sup. You can put config.pro in working directories and load them once you have started ProE.


Configurationfiles are read from the installation directory for ProE in the text folder. Another location for the files is your login directory on your computer.

Yeah its obvious, but i have stored my config.pro in proe/text directory. One thing i checked that is: i just copied config.pro in text directory to startup directory and i had given a path to my startup directory to use config.pro. After some time ikilled one mapkey andoverwrote on that config.pro which is in startup directory. I opened proe after that mapkey is still alive.


But i tried to kill the mapkey and overwrote on config.pro which is in text directory which works good.

 

[Guest]

My post was really intended to help you with the tool bar locations. I was just using the config.pro as the example. I haven't worked with mapkeys so I don't know how they are handled with different config.pro files in different locations.


You may have picked up on what I saying, but I'm not sure. My point was that if you have mutiple configuration files, config.pro, config.win, model_tree.cfg in multiple directories you need to know in what order they are loaded. The ones in the startup directory are loaded last. If the config.win in the proe/text directory is the one that has options you want loaded, and you have a config.win file in your startup directory, as I see it you have three options.


1. Delete the config.win file in the startup directory. By doing this, the config.win file in your proe/text directory will be the last file loaded as long as there isn't a config.win file in your login directory.


2. If you keep the config.win in the startup directory, you need to make sure there are no conflicts with the tool bar locations. If there are conflicts, the most recently loaded setting will be used.


3. Once your in ProE, load your settings from the Customize Screen dialog box.

 

[dgs]

kd2007 is right. Config files (both config.pro and config.win) are read first from the <loadpoint>/text folder, then your 'home' directory (defined by OS) then the start up directory (defined by the Pro|E launch icon).


An important thing to remember is they both are cumulative. Each config.pro or config.win loaded adds to the last. If a single option exists in both files, the last one loaded wins.


For config.win files, I've found that loading more than one file can produce unpredictable results. It can be done (we do it here), but I'd separate the parts of the UI that each file controls. For us, the company config.win (in the text folder) only changes drop down menus, the user config.win (in the startup folder) controls everything else.

 

[Asho Pulsar]

I didn't faced any problem with config.winwhich is placed in the startup directory. It works well and good. The problem is with config.pro only. In the case of mapkey deletion, Config.pro which is in the startup directory is not accepting any changes made but the config.pro which is in the text directory is accepting all the changes. Do i making any senseless?

 

[Guest]

Hi,


Can someone tell me that where exact location to be set and save the config.win so that modified toolbar locations has to be same place when i open the proe again.


Thnx in adv.

As I said, my post was ment to help with your initial post. I tried creating a simple mapkey, so I think I understand your prblem now. Your problem, as I understand you, is that you created a mapkey, tried to change, delete,or overwrite it, but when you close ProE and restart the changes are not reflected. Without knowing how you are trying to do things it is difficult to tell you where your problem is coming from. But here is what I found.





I created a mapkey to open a new file and saved it to config.pro in the startup directory. I modified the same mapkey to create a new part and saved thisconfig.pro in my login directory. Both work the way they should when opened. When I used the mapkey dialog box to delete the mapkey it was removed from the dialog box and I saved the config.pro file. I closed ProE and restarted. I opened the mapkey dialog box and the mapkeywas still there. The reason for this is the map key is still present in the config.pro file in my login directory. Another thing I noticed is that when I deleted the mapkey and savedthe config.prousing the All button under my login directory, when I closed ProE and restarted, the mapkey is still there in the mapkey dialog box and the config.pro file. I don't know if this is a bug or if it only allows you to save to the config.pro in the startup directory. The way around this is to open the config.pro file under the Options menu and delete it there. Save the config.pro file (in your case the file in your proe/text).





Again, the point is, you have a conflict somewhere in one of your config.pro files. You need to check all the ones in the ProE default search directories (proe/text, your login directory, and startup).

 

[Asho Pulsar]

Again, the point is, you have a conflict somewhere in one of your config.pro files. You need to check all the ones in the ProE default search directories (proe/text, your login directory, and startup).

Another thing i tried, i deleted the config.pro which is in the text directory and then i used config.pro in startup directory. Again i deleted one mapkey and override it to the startup directory. Got the same result, mapkey not killed!!!

 

[dgs]

The mapkey editor isn't really set up to do anything well except record, change& save mapkeys. removing them can't be done there, it seems to only delete them from session, not the config file.


Have you tried to go into the config editor, as kd2007 said? Delete your mapkey there. You can look in the drop down list in the upper left to see what config files are loading. Select them one at a time and look for your mapkey statement. Once you find it delete it, but look in the other files too in case it's duplicated.


Another thing is that when you save changes to a mapkey, many times Pro|E simply adds a new mapkey statement to the config file. There may be several of the same mapkeys in there, but only the last one gets read. I'm not sure if deleting the mapkey entry through the options dialog deletes all instances of the mapkeyor just the last one. That could explain how you can delete it and it's still there. If there are5 copies in the config file, you may have to delete it 5 times. Opening the config.pro file in a text editor like notepad is the way to check for that.


Pro|e also has a habit in certain circumstances of creating new config files named 'current_session.pro' when you save from the options dialog. These then contain all the settings from all other config files in one file. You may have one of those in your home directory. Check for it in that drop down list in the upper left of the options dialog.


The config file system is pretty good in many ways, but the GUI for managingit is pretty lacking. I donearly allof my config file management in a text editor.

 

[Guest]

Can you take me through your menu picks on how you are performing this or show me what is in your config.pro file. I believe someone pointed out in another thread that you may have more than one line for the same mapkey in the config.pro. I found this after I posted last. If you start out with a mapkey and delete it using the mapkey dialog box, it deletes the mapkey "in session". It does not delete the line from the config.pro file. If you stay in ProE the mapkey does not work. If you close ProE, restart, and then use the mapkey it functions the same as it did before because it reloads it and it is "in session". Here are some pictures of what I tried.

Notice the grey dot by the second mapkey, this means it is "in session". I deleted the mapkey and checked the config.pro again.











Notice the mapkey line is not deleted but the status dot has changed. The mapkey has been deleted from "in session". Continueing in ProE without closing, the mapkey does not work.I then closed ProE, restarted, and checked config.pro. Both lines are still in the file but the status has changed to being "in session" (See first picture). I then deleted the lines from config.pro, saved it, and opened it from the options menu. Without restarting ProE the mapkey still worked. The reason for this is the mapkey is still "in session". Opening up the mapkey dialog box, the mapkey I deleted is still there. Deleting it from the dialog box the mapkey no longer worked. I then closed ProE and restarted. When I tried the mapkey it didn't work. When I checked the config.pro there were no mapkeys since I saved it that way and there were no mapkeys when I opened the mapkey dialog box because there were no mapkeys to load fromconfig.pro.





As I said before, you have a conflict somewhere you need to find where it is. I suspect now that your problem is that you opened ProE, deleted the line from the config.pro, saved it, and without exiting and restarting tried to use the mapkey. At this point your mapkey is still "in session" (check mapkey dialog box). If you did exit and restart, it appears that you have multiple lines for the mapkey in the config.pro and they didn't get deleted. So when you restart they get loaded "in session".

 

[Asho Pulsar]

Pro|e also has a habit in certain circumstances of creating new config files named 'current_session.pro' when you save from the options dialog. These then contain all the settings from all other config files in one file. You may have one of those in your home directory. Check for it in that drop down list in the upper left of the options dialog.


The config file system is pretty good in many ways, but the GUI for managingit is pretty lacking. I donearly allof my config file management in a text editor.

Dgsyou arecorrect, I got few current_session.pro on my hard disk. I deleted all the current_session.pro and i used config.pro which is in startup directory which works well. Now i deleted the mapkey which was saved as few more times in that config.pro opened by manually as a notepad.



Edited by: Asho Pulsar

 

[Guest]

I guess that is another thing that is annoying, the way ProE likes to create a versioned files for things when you change something. I find it helpful with models and assemblies, but for configuration files I don't find it helpful at all. I almost forgot about the current_session.pro files since I don't use them anymore. They caused more problems for me than they are worth. Anyway, goodto here you found the problem.

 

[Asho Pulsar]

cheers

 

[bunterhund]

in the new version of crossfire (there's a free english version somewhere in the web)you can also manageyour mapkeys AND edit them. The right mouse button in the list opens a dialog where you can list all your mapkeys, then select one, and jump to it..






Edited by: bunterhund

 

[anandel]

in the new version of crossfire (there's a free english version somewhere in the web)

 

[ReinhardN]

http://www.geocities.com/arossbach/proe.html

 

[bunterhund]

Hi anandel !


ok, I