ProStructures Configuration Variables

The backstage tool (File > Settings > Configuration > Configuration Variables) is used to open the Configuration Variables dialog. The ProStructures CONNECT Edition Configuration Variables are seen in the ProStructures category of Configuration Variables dialog.

This section lists the configuration variables recognized by the ProStructures, Rebar, and SMC applications in the CONNECT Edition. A description, the variable type, and the default setting are included for each variable.

The variable types are as follows:

Variable type	Default setting
Boolean	When set, 1, true, or on is interpreted as true. Not set, 0, false, or off is interpreted as false.
Keyword	One of an expected set of strings.
File name	The name of a file-with extension, but without path.
File	Full path specification for one file
Directory	Full path specification for one directory. The path must be terminated by a forward slash "/"..
File list	One or more full path specifications for files separated by semicolons. Wild cards are supported, e.g. $(VARNAME)subfolder/*.mdb
Directory list	One or more full path specifications for directories separated by semicolons. Each directory path must be terminated by a forward slash "/".
Enhanced directory list	One or more full path specifications for directories separated by semicolons. Wild cards are supported in the last (leaf) name, e.g. $(VARNAME)subfolder/Jansen_*/ Note: The Enhanced directory list configuration variable type is recognized only by the ProStructures application.

Configuration Variable File Syntax

Configuration variable files are plain-text files where each line contains a configuration variable and definition.

Variable Syntax

<VARIABLE NAME><operator> <new_value> # optional comments

Where:

Syntax

Description

The name of the configuration variable being defined. Most variable names used by MicroStation begin with MS_ or _USTN_.

Note: Variables names beginning with an underscore, _ , are not displayed in the Configuration dialog.

Variable names can contain only alphanumeric characters (A-Z, 0-9) and must be at least two characters long. Although variable names are not case sensitive, uppercase letters are used by convention. There is no limit on the length of a variable name, but as a practical matter it should be kept under 32 characters. White space (space or tab characters) before and after the variable name is ignored.

The following operators are used between the variable name and value:

Operator	Description
= (equals)	Assign the <new_value> for use as <VARIABLE NAME>. This overrides all previous definitions at or below the current configuration variable level.

: (colon)

Assign the <new_value> for use as <VARIABLE NAME> only if the variable does not already exist.

+ (plus)

Append the <new_value> to the current value of <VARIABLE NAME>. Uses a space as a separator.

Note: This operator should not be used for directory or file lists.

> (greater than)

Append directory or file lists defined by <new_value> to a variable definition that defines a path. If no current value for <VARIABLE NAME> exists, this is equivalent to the = operator. Otherwise, it appends a path separator character —a semicolon, ; — and then <new_value>.

< (less than)

Prepend directory or file lists defined by <new_value> to the beginning of a variable definition that defines a path. If no current value for <VARIABLE NAME> exists, this is equivalent to the = operator. Otherwise, it prepends <new_value> followed by a path separator character —a semicolon, ;.

<new_value>

The value used for the <VARIABLE NAME> when this configuration variable file is used.

# optional comments

You can annotate the configuration variable file by including a number (also referred to as a pound or hash) symbol, #, after the definition. Anything after a number sign on a line is treated as a comment and is ignored.

Note: File paths for directories (Windows folders) should be use only forward slashes (/not/ back slashes) and should end in with a trailing forward slash.

Preprocessor Directive Syntax

%<preprocessor directive>

Base Paths

Units System

User Interface

WorkFrames

Structure Property Catalog

Materials

Classification

Shapes

Plates

Mechanical Fasteners

Welds

Bracing

Handrails

Joists

Stairs

Dispatch Cells

User Parts

Concrete Modeling

Rebar Modeling

Connections

EEDs

Position Flags

Details

North Arrows

Elevation Flags

Partlist

Exchange

Rebar Application

SMC Column Grids

Miscellaneous Data Files

Parent topic: Configuration