Configuration Variable Period

I'm just wondering how MS finds the destination path, behaviourally, if it does not know the inbetween heirarchy... or does MS just keep searching up the tree until it finds the first 'matching' path and use that?

Anyway if it doesn't work I'll scrap it.

Thex1138:

Results in..J:\99999\..\tretert\

BTW: This is a valid path, maybe not the shortest possibility, but it works.
Sometimes it could be easier to define a help-variable with a root path. At least there are many good possibilities to work with.

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.

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?

®

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

Just curious, but have you looked into configuration file preprocessor directives?

[edit: What Michael identified... :)]

better use {parentdevdir $(A123456789)}tretert/

not sure if we used  ../ ever, but changed our customers configs to use the parentdevdir variant.

HTH Michael

PS: maybe you need to evaluate the content of A111111

I tried a couple of variations of this but don't get the right result...

A123456789 = J:/99999/
A111111 : $(A123456789)../tretert/

Results in..

J:\99999\..\tretert\

Bentley does :)

 i.e.  ...\TriForma\config\appl\intmgr.cfg
Line 72 - IFM_CONFIG : $(TFDIR_MDLAPPS)../config/