One of the unique features of the ProSig program is its flexible use of component files. In certain cases of multiple project management, special project requirements may necessitate a variety of different dataset inputs in these component files.
The same is true when it comes to the use of project-specific blocks.
Part of the program is to manage the access to specific blocks and data by means of flexible search paths in the environmental settings.
All access to directories defined here is hierarchy-based. In other words, when searching for a component file or block, ProSig successively goes through search paths 1 to 3 (those that are occupied, that is.)
If the file in question is found, the program ends its search right there. If it is not found, the program takes the same file from the own ProSig standard paths for component files/blocks.
Saving the use of access paths to specific projects requires prior adjustment of the "DWG2PRJ.LSP" function. Since this, in turn, requires Lisp programming skills, it is recommended to contact the ProSig Development Team in this case.
The standard application does not require any changes to your environmental settings.