Search path....

[jelston]

I am about feed up with Pro/E's crap!!! Now, it decided not to use the search path i added to the config option, so i have to find parts individually. Anyone dealt with this problem before? Any suggestions?

 

[dgs]

Was the search path working before? Wheredid you store the search_path line, config.pro or config.sup? Where is the config file saved?
Edited by: dgs

 

[prohammy]

Jelston,


Check your config.pro and make sure that every option search_path is looking for teh correct directoty


Kev

 

[prohammy]

Perfect double posting form myself and dgs (ha, ha, ha)

. THat'll teach me to get a cup of coffee right in the middle of posting

Kev
Edited by: prohammy

 

[dgs]

If it worked once, but now isn't, it sounds like an issue with the config not loading. Could be a lot of reasons for that.


If you just implemented the search_path line and it isn't working, I'd say it's a typo in your path.

 

[jelston]

It was working before. The config.pro file is in the text directory (and working directory for that matter)and still not being found.

 

[dgs]

Hmmm. Are you using drive letter paths? Pro|E can sometimes get flaky with other kinds of paths. Also, if there are spaces in the path it can be flaky as well.


I'd double check the path just to be sure. Maybe an upper level folder got renamed or something?

 

[jelston]

My search path was working Friday. I have not touched it since and I am the sole user of Pro in our company.

 

[jelston]

Okay,


Now, for some reason, i have to open the config menu select the search path that i am interested in and select apply every time i restart pro/E. Suggestions? 12 gauge maybe?

 

[prohammy]

It was working before. The config.pro file is in the text directory (and working directory for that matter)and still not being found.

Jelston,


I have a feeling that this may be your problem. You should really only have one config that the system can pick up on. Try deleting the one in the text directory and see if that helps


Kev

 

[dgs]

Jelston,


I have a feeling that this may be your problem. You should really only have one config that the system can pick up on. Try deleting the one in the text directory and see if that helps


Kev

Actually, that's not true. Config.pro files are additive, meaning that new files add to the old. If there's an option in 2 files, the second one loaded overwrites the first. There are exceptions for options like 'mapkey' and 'search_path' where multiple instances of the option is valid.


We load as many as 4 config files at start up - company config.sup, company config.pro, user config.pro and client config.pro.


That said, if the exact same option is in there twice, it may cause problems. I'd try removing the second config file (working directory) or at least the search_path option from that file.


You may also want to look at putting your search path statements into a search path file (search.pro) and using the config option 'search_path_file' to point to it.

 

[wsylvester]

for piece of mind when working with assy.


i have config options set;


display_full_object_path yes
info_output_format text
info_output_mode file


that way I can do a info>model>top level... and a inf file is wriiten with full paths , so if I have trouble later down the road ... I can refer to the file

 

[jelston]

[/QUOTE]


You may also want to look at putting your search path statements into a search path file (search.pro) and using the config option 'search_path_file' to point to it.


[/QUOTE]


Is it possible to do this with mapkeys too?

 

[dgs]

You may also want to look at putting your search path statements into a search path file (search.pro) and using the config option 'search_path_file' to point to it.


[/QUOTE]


Is it possible to do this with mapkeys too?


[/QUOTE]


Mapkeys.pro - great idea! Not possible, as far as I know.


You could have a separate config.pro for mapkeys and another for other options. Put the 'standard' one in the text folder adn the 'mapkeys' on in the home or 'start in' folder. They would both be loaded at startup.


You could also write a batch file that would combine multiple config files into one at run time, placing the resultant file in the text folder and then calling Pro|E.

 

[jelston]

Oh, i guess my seams were showing on the last post

Anyhow, since i put the search path into file format, Pro/e will find absolutely nothing. Any specifics about listing search path in format? I already have the complete file location.

 

[dgs]

... since i put the search path into file format ...

Not sure what you mean by 'file format'. The search path should be the complete directory path only, not to a specific file. You're telling Pro|E where to look, not what to look for.


For example:
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">


search_path c:\this_is\the_folder\to_look_in</BLOCKQUOTE>


Not:
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">


search_path c:\this_is\the_folder\to_look_in\my_part.prt</BLOCKQUOTE>


Does that help?

 

[jelston]

the 'search_path_file' option asked for a specific file which if i am understanding correctly is search.pro.

 

[dgs]

Ah, sorry, my bad.


The search.pro file should contain any number of instances of the 'search_path' format, as listed above. The format for the config.pro option for search_path_file is:
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">


search_path_file p:\here_is\my\search_path_file\search.pro</BLOCKQUOTE>
Does that help.

 

[jelston]

just one question (before the next one

) should 'search_path' be listed in the search.pro file. For example, when i open the search.pro file, should look something like this:


search_path C:\Documents and Settings\jelston\My Documents\ProEngineerFiles\monitors\MONITORS\COMMON PARTS



search_path C:\Documents and Settings\jelston\My Documents\ProEngineerFiles\monitors\MONITORS\NGM204S

 

[dgs]

Yep, you got it.


The lines inside the search path file are the same as they would be in the config.pro file.


Now, I see that you have spaces in the path (Documents and settings for example). I'm not sure if that's a problem or not. In the past it has been. You might try putting the entire path in quotes, but I don't know if that's supported or not.