I use these settings to have libraries at hand in my project directory, even when working in subfolders.
MS_DGNLIBLIST > $(_DGNDIR)*.dgnlib #find DGNLIB in current folder. MS_DGNLIBLIST > $(_DGNDIR)../*.dgnlib #find DGNLIB in a higher folder. MS_DGNLIBLIST > $(_DGNDIR)../../*.dgnlib #find DGNLIB in a even higher folder.
MS_CELLLIST > $(_DGNDIR)*.cel MS_CELLLIST > $(_DGNDIR)../*.cel MS_CELLLIST > $(_DGNDIR)../../*.cel
Ivo Blaauw= = = = = = = = = = = = =Look what the CAD dragged in...
Thanks all for your replies!
I have an extensive set of documents on pre-processor directives which I am familiar with including 'pardir'
.... and then I saw the '..\' '..\..' and '\..' in a recent post and I have tried to implement them, as well as the single '.' in some configuration syntax.
So I am learning about them and how I can use them effectively.
Cheers
/Rob
P.S. Ivo, what resulting config variable value do you get from those directives?
®
CADMinistrator ®
MS_CELLLIST : Cell files shown in the Cells dialog pull down menu.
_DGNDIR: This is the folder in which the current file resides. This off course is can be different each time you open a file.
> : Add a value/setting to existing values.
MS_CELLLIST > $(_DGNDIR)*.cel #find Cell-libraries in the current folder. Put a Cell file in the folder you're working in, and you'll never have to search for these cells.
MS_CELLLIST > $(_DGNDIR)../*.cel #find Cell-libraries one level higher then the current folder. So you'll still find the cells, even when working in a subfolder.
MS_CELLLIST > $(_DGNDIR)../../*.cel # Same story... now applicable when working in a sub-sub-folder. Same works for MS_DGNLIBLIST > $(_DGNDIR)../*.dgnlib #find DGNLIB in a higher folder.
In these previous cases, the libraries can be added to the folder, without having to restart Ustation. However, linestyle resources do not allow to be read this way, from a flexible location.