34 setup

This object cannot be defined; it can only be queried in the rules!

Events

none

Children

none

Parent

none

Menu

none

See Also

C function DM_ParsePath in manual “C Interface - Functions”

34.1 Attributes

34.2 Specific Attributes

The object messagebox ignores the .overridecursor set at the object setup and always displays the cursor defined for this messagebox or the default cursor.

Example for the Display of the Overridecursor

Msgbox1.cursor := setup.overridecursor;

querybox(Msgbox1);

Msgbox1.cursor := null;

You may change the variant of a text resource also during runtime, namely in the

• Rule Language
• programming language

So far the language was determined on starting an application with the command line option -IDMlanguage.

Rule Language

setup.language := <variant number of language>

Example

text "Language" //  English (default)

{

  1: "Language"; //  German

}

on MENUITEM_LANGUAGE select

{

  setup.language := 1;

}

C and COBOL Interface

The corresponding variant number of the chosen language has to be assigned to the setup object with DM_SetValue.

Note

It is helpful to set the language before loading the dialog as the text of every visible object has to be changed. If no object is visible yet the language may be changed very quickly.

34.3 Access to Environment Variables

The environment variables of the program can be set using the setup object. For this purpose there are the two attributes .env[] and .envvar[].

.env[] contains all environment variables. Values which have been set with the option -IDMenv overwrite the values set in the environment.

Variables which have been set with the option -IDMenv are valid for IDM functions only. With the attribute .envvar[], however, you receive environment variables only.

The attributes .env[] and .envvar[] are gettable and settable. They are indexed with the names of the environment variables. If the environment variable has not been set, a fail is returned on querying.

In addition you may view all variables which have been set with -IDMenv. Use the attribute .count[] for this purpose. It is indexed via .env whose return value is be the number of IDM environment variables. Now .env[] can be indexed with numbers from 1 to .count[.env] in order to find out the names of the environment variables.

Example

!! Reading the PATH variable
print setup.envvar["PATH"];

!! Setting an IDM environment variable
setup.env["DIALOGPATH"] := "/usr/local/idm/examples";
load("DIALOGPATH:draw.dlg");

!! Reading all IDM variables
for I:=1 to setup.count[.env] do
  print setup.env[I]+"="+setup.env[setup.env[I]];
endfor

!! Deleting the variable
setup.env["DIALOGPATH"] := null;

!! Setting an unset environment variable
if fail(setup.env["SERVER_OPT"]="") then
  setup.env["SERVER_OPT"] := "true";
endif

Note

Environment variables which have been set during a process will not result in changes in the environment variables of parent processes (e.g. shell) or existing child processes. Only new child processes can receive the changed environment variables.

34.4 Attributes for Controlling the Tracing

The setup object provides several attributes to control the tracing:

.errfile, .logfile, .tracefile, .tracetime and .tracing.

See Also

Chapter “Tracing” in manual “Development Environment”