Search path....

[wsylvester]

jelstom


watch_out_for_spaces


avoid_if_possible

 

[tbutler]

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

I think dgs is correct, put quotes around the paths that HAVE to have spaces in them. Also, I have a search file set up to find the different formats that we have for our customers and inside that file I don't have each path pre-cursored with search_path I just have the drive letter and then the folders inside that drive to the folder that I want it to look in. Not sure if this is the same thing or not.


Todd

 

[jelston]

I would like to use the searchfile but I haven't been able to get it to work at all. The search_path works sometimes (takes a little massaging) , so until i get the time to tinker I'll probably just run with that.

 

[jnoval]

I don't think you need "search_path" words in search.pro. You should only need "search_path" wordsif you have the search_path in config.pro


EX. Search.pro


p:\models
p:\models\house
p:\models\hardware

 

[mjcole_ptc]

You can either list all search paths in your config.pro so that they always get loaded in this case you'd write many lines with search_path and directory to search. Or have a file called search.pro that contains the search paths that you can point to by using the search_path_file option which allows you to keep a separate file that lists the directories so you can keep your config.pro file smaller.
search_path_file C:\path\to\search.pro

then you just need a line with each path to search listed in search.pro which is just a list of directories to search.

Michael

 

[bunterhund]

...and when you want to be shure the syntax of this fileisok you can simply use the search-pro-generator (freeware).


[url]http://www.geocities.com/arossbach/proe/search_pro_generator _engl.zip[/url]

 

[jnoval]

Or in a commandprompt use:


dir /ad /b /s >search.pro

 

[mgnt8]

This post has been a lot of help. Ialso thought search paths were a joke until I read about the quotes. Now they work great. Wish I would have found out about that about 8 years ago. Incidentally, PTC says the only config.pro options that support quotes are 'search_path' & 'pro_colormap_path'. Here's the TAN on the subject. Apparently, there's been an open SPR on this problem for years.

 

[jelston]

Sorry to beat a dead dog fellas, but it still ain't working.

UPDATE!!!


After vast amounts of experimenting and research, i have found yet another dislike of this finicky (hope that's spelled correctly), moody, tempermental program. If your total search path is too long or individual sections are longer that some certain number which i didn't have the patience to find, your search path won't work. In short, KISS it. Keep It Short S_ _ _ _ _ (Fill in your favorite 's' word).
Edited by: jelston

 

[dgs]

Yeah, there's an undocumented (or at least I couldn't find it documented) limit to config line length. In practice I've found it to be about 95 characters. With mapkeys, putting ;\ at the end of the line tells Pro|E to keep going to the next line, but I doubt that would work with search paths.


Another thing you can do is add a line like this to your config file (all on one line, the forum wraps it):


123456789_123456789_123456789_123456789_123456789_123456789_ 123456789_123456789_123456789_12345


That shows you how long 95 characters is so you don't exceed it.


The nice thing about using a 'search_path_file' is that you then don't need the 'search_path ' text, which will save you 12 characters per line.

Edited by: dgs

 

[bunterhund]

perhaps this could help: here


http://proe.cad.de/programme/search_pro_manager_engl.zip


is abutton where you can change the paths into the old DOS syntax.