search.pro

[mechbull]

is the only way to add new places to the search pro is to manually add them by opening the search.pro or is there an icon i am supposed to click when saving or ??????????

 

[mechbull]

ps: if it is only intended that you manually add these is it possible to write a batch file to add a new directory into the search.pro

i have a mapkey that launches windows explorer to what ever my working directory is (maybe build off this)??

 

[telecomguy]

Here's a quick way of generating a search.pro from the DOS command line. Change directory to the top of a directory tree you want searched and then execute:

dir /ad /b /s > tree.txt

Then you can copy/paste from tree.txt into your search.pro.

I'll be thinking about your idea of creating a mapkey/batch file to add an individual directory from within ProE. One thing to note, Pro only reads the search.pro at the beginning of the session, so you would have to get out and back in for it to take effect.

<tg>

 

[mechbull]

thats even beeter than what i have done
i found a program called directory printer (better for other things)
but works as well

thanks telecomguy

 

[dgallup]

Why don't you just show the address bar in windows explorer? Then you can just copy the directory path and past it into your search.pro.

 

[mechbull]

yes i started doing it that way but looked for other ways because there were nearly 150 folders to add in

 

[cadcamguy]

With the config option display_full_object_path yes
when you do a top level info of a assembly you will get a full path of parts and sub-assy in the .inf file which you can parse out and create a search.pro file from.

So you can build your assy grabbing whatever you want, then create a search.pro for that assy and save that in the work dir.

Then you have "as needed" search instead of a "all inclusive" .

 

[telecomguy]

I've always wondered how the # of directories in a search.pro impacts retrieval time for a large assembly. Because ProE only reads the search.pro at startup, do you suppose they are building an index of files at startup so it can find things quicker? If so, then there would really be no value in having an 'as needed' vs 'all inclusive' search.pro.

<tg>

 

[Hora]

I don't think the # of folders to search for components will slow down the retieval of components. But where the folders are installed, yes. I mean if you search thru a slow or a busy network or server, that will be long. Even when you save components. But if you search in your local computer folders, there will be no speed lost. Also the type of the HDD is essential. It will take longer time to retrieve parts from an ATA or SATA drive than a SCSI drive.

-Hora