More fun with Buttons

[Rbrgr83]

I apologize for all of the menu related questions in the modeling section. Last one, I swear.


Ok, so this one is a bit of a puzzle. Let me start with my setup:
Everyone in my group is working in ProE with a common config.pro file in a public directory. There is also a common config.win file that just has the defaultmenu/button settings. We've been playing with the idea of everyone having a local config.win file which they load every time they start ProE. Upon implementing this method we seem to have stumbled upon a problem.


There is something funny happening with where ProE is looking for my config.pro file. It loads properly from the public folder. However, I've noticed that when I look in the options dialog box, it also lists a config file that I have copied into my private folder on the network.


A co-worker of mine also has the same occurance, but his is in an entirely different directory. His is in the 'Docs & Settings/Username' folder (one up from My Document) on this hard drive. We've tested this, and sure enough ProE always looks in this one extra folder (respectively) for a config file when it loads. Also, if we place our personal config.win file in this dir, it loads it automaticaly on startup (even though it's loading the config.pro from the public dir).


I just want to know if anyone has experienced this before? Why is ProE looking in another directory than the start point I have setup for it (which is common for everyone in my group.) Why would the second directory be so different for the two of us?


It's entirely possible that we had each, at one point, loaded a config file manualy from these respective dirs and that is why it keeps looking back there. However, we did try to replicate this process ourselves and it did not work.


Any ideas? I'm spent --->

 

[ReinhardN]

http://www.mcadcentral.com/proe/forum/forum_posts.asp?TID=34 574&PN=1

 

[Rbrgr83]

Ok, so from that post, Jnoval stated:


Proe is lokking in 3 places for the files.
1. ..Wildfire3\text
2. Users home folder
3. Working dir (Only on start up of Proe, and not if you change working dir from proE)


My concern is that ProE is also looking in a 4th dir. This 4th dir is different for me and my co-worker (and on completely different drives for that matter). Neither was set in the config file (or a search file).


This is my big question. Why would ProE even look in this 4th folder if I have not told it to do so? More importantly, why does it give preference to the settings in this dir over those in the working dir (startup point).

 

[DL_allainmfg]

Did you check the properties of your shortcut (if you use one). you can set a target directory through there. Maybe you changed some settings since the shortcut was created ?

 

[Rbrgr83]

No, this would be #3, the startup point.

 

[mjcole_ptc]

If you don't point to any customize screen .win file in your config the company one from the install directory text will load and you can then Use the customize screen dialog to load your own config_abc.win no matter what Pro/E has already loaded.

Michael

 

[Rbrgr83]

I don't think that is correct. First of all, I don't believe there is an entry in the config.pro to point to a specific .win file. Second, the /text dir is the first place that ProE is going to load from, so if any settings are going to be overwritten, it's the settings that load first.


I think I know what you are saying though. If I don't have any settings in my public dir (#3), then there will be nothing to overwrite my settings from 1 and/or 2.


At any rate, I have more or less solved this problem as it applies to ProE.The original problem I put forth i've found is related to the "home path" (#2).


I'm currently trying to figure out if I can change the "home path" or "home drive" settings that windows uses. This is really a windows question rather than a ProE question, but I figure someone here is astute enough to know the answer.

Thanks for the help everyone.

 

[ReinhardN]

Is there a config.sup somewhere ? It will override every option made in the above mentioned folders.
You can see which config.pro are used under #tools #options

 

[Rbrgr83]

....