# Structure of Editable Settings Files, editing in the general text editor

Editing the files can also take place outside the program system in a standard text editor. Changes are not loaded automatically in project management or in the building. Therefore, the following procedures must be followed:

* To edit the file, the calling function in project management or the building should be exited.
* When the function that uses the editable settings file is called, it is also reloaded.
* Standard - Functions from *Manage Settings* are to be used only if the settings file is not open in a text editor.\
  Note: Unfortunately, it is not always possible to determine that a file is currently open, because, for example, Notepad++ opens only a copy of the file automatically.

&#x20;

Any erroneous entries are possible here and cannot be intercepted by the program. The file may become unusable. **Therefore, only experienced users should edit these files with a general text editor.**

### Structure and contents of editable settings files

In editable settings files, there are structures and areas that can be changed in the editor and others that should not be changed. In many of these files, corresponding entries and comments provide notes on the purpose and contents of the file.

If a reference in the form #123 (crosshair with number) is specified as text, then this is the reference to the line number in Editdsi1.frg.

The files are divided into data areas, so-called *sections* . Each section begins with an entry in square brackets and ends with the same entry supplemented by the word ENDSEC:

`[`*`SECTION NAME`*`]`

`...`

`[`*`SECTION NAME`*` ``ENDSEC]`

Within the *section* each line consists of keyword - equals sign - value. A comment may then follow, separated by a double slash.

*`Keyword`*` ``=`` `*`Value`*

*`Keyword`*` ``=`` `*`Value`*`//`*`Comment`*

&#x20;

### Structure version of the file, \[VERSION]

Editability: Do not change!

In the *section* VERSION contains the identifier for the structure version of the file. The program requires this information in order to process the file correctly. This is not the version of your data. This *section* must not be changed.

Example:

`[VERSION]`

`Version=1.1`

`[VERSION ENDSEC]`

### Groups, \[CATEGORY]

Editability: Preferably edit with *Manage Settings* .

The *section* CATEGORY contains the names and order of the groups. The keywords end with a number corresponding to the order. After the equals sign, the name of the group follows:

Example:

`[CATEGORY]`

`CategoryName1=`*`group abc`*

`CategoryName2=`*`group 123`*

`[CATEGORY ENDSEC]`

### Information about the file, \[FILE INFO]

The *section* FILE INFO contains information about the file and the data defined in it. Valuable notes on the data and rules in the file are provided here.

If a reference in the form #123 (crosshair with number) is specified as text, then this is the reference to the line number in Editdsi1.frg. In the dialog for editing the editable settings files, the texts from the frg (language file) are displayed.

Up to 5 lines of text can be assigned to the keywords FileDescription\_1 through FileDescription\_5.

Example:

`[FILE INFO]`

`FileDescription_1=`*`Description of the file`*

`FileDescription_2=`*`max. 5 lines`*

`FileDescription_3=`*`#123`*

`[FILE INFO ENDSEC]`

### Information on the sections, \[SECTION INFORMATION]

Editability: Information must be present for each *section* ! Note the individual entries!

All settings of the file contain the same *sections*. System information is the same for all these *sections* regardless of which setting they are in. Therefore, this information is recorded in this upstream *section* . Settings do not have to contain all of these *sections* but may contain only *sections* that were defined here.

The *section* SECTION INFORMATION contains all *sections*, which can be used in the settings. For each *section* there are information texts, the SectionsType and the reference to a help image:

**Line1 .. Line5**

Up to five lines of explanatory text on the content of the *section*. Valuable notes for editing the file are provided here. If a reference in the form #123 (crosshair with number) is specified as text, then this is the reference to the line number in Editdsi1.frg. In the dialog for editing the editable settings files, the texts from the frg (language file) are displayed.

**SectionType**

There are 3 types of *sections* distinguished: FILTER, FREE, FIX

***FILTER***      The keyword before the equals sign describes a selection of designs (wall, ceiling, roof surface) or a selection of ID numbers.

The following selection descriptions are possible:\
\&#xNAN;*ABC123*  the full name is ABC123\
\&#xNAN;*ABC*\*    the name begins with ABC\
\**ABC*    the name ends with ABC\
\**ABC*\*   ABC appears somewhere in the name.

In these *section* any number of entries can be made. The parent function determines whether all matching entries are used, only the first, or only the last.

***FREE***         The keyword before the equals sign can be assigned freely. These can be, for example, user variables.

In these *section* any number of entries can be made.

***FIX***           The keywords before the equals sign and their number are fixed. In these *sections* the possible keywords are already entered. No additional ones can be added. Keywords that are not used should simply remain without an assigned value.

ReferenceImagePath  Reference to a help image. This is displayed in the dialog for editing the editable settings files.

&#x20;Example:

&#x20;`[SECTION INFORMATION]`

`[`*`SECTION A`*`]`

`Line1=Text for section A`

`Line2=max. 5 lines`

`Line3=#123`

`SectionType=FILTER`

`ReferenceImagePath=%DHPABB%\GWE___04.bmp`

`[`*`SECTION A`*` ``ENDSEC]`

`[`*`SECTION B`*`]`

`..`

`[`*`SECTION B`*` ``ENDSEC]`

`..`

`[SECTION INFORMATION ENDSEC]`

&#x20;

### Settings, \[DATASET EDITDSI]

The actual settings are defined in the sections DATASET EDITDSI.

* There is such a *section*. The *section* Name is always the same, so it does not contain a running number or the name of the setting.
* The display order of the settings corresponds to the order in the file.

&#x20;

`[DATASET EDITDSI]`

`...`

`[DATASET EDITDSI ENDSEC]`

`[DATASET EDITDSI]`

`...`

`[DATASET EDITDSI ENDSEC]`

&#x20;

Each of the settings first contains the information about the setting:

**Name**                         The name of the setting with which it is displayed in *Settings selection* . The names of the settings in a file must be unique; no name may be assigned twice.

**CategoryName**            Group to which the setting belongs. Possible groups are listed in the *section* CATEGORY.

**ReferenceImagePath**  Reference to a help image. This is displayed in *Settings selection* and can be very helpful for the operator.

The assignment of the help image should be done in *Manage Settings* , as the possible references in the paths are entered automatically here.

&#x20;

This is followed by the actual data*sections*. These were defined earlier in the *section* \[SECTION INFORMATION].

&#x20;

The comment for the setting is stored in the last *section* in this setting: \[DATASET EDITDSI MULTILINE\_STRING] Using the keywords Line1 through Line5, up to 5 lines of comment text can be specified. This is displayed in *Settings selection* and can be very helpful for the operator. The comment can also be entered in *Manage Settings* .

&#x20;Example:

&#x20;`[DATASET EDITDSI]`

`Name=`*`Dataset one`*

`CategoryName=`*`group abc`*

`ReferenceImagePath=%DHPABB%\DietrichsLogo.png`

`[`*`SECTION A`*`]`

`AW*=(WL<12.0[m])`*`//use double slash for commentary`*

`[`*`SECTION A`*` ``ENDSEC]`

`[`*`SECTION B`*`]`

`..`

`[`*`SECTION B`*` ``ENDSEC]`

`..`

`[DATASET EDITDSI MULTILINE_STRING]`

`Line1=`*`Text for setting Dataset one`*

`Line2=`*`max. 5 lines`*

`[DATASET EDITDSI MULTILINE_STRING ENDSEC]`

`[DATASET EDITDSI ENDSEC]`

&#x20;

### Data lines

Within the data *section* each line consists of keyword - equals sign - value. A comment may then follow, separated by a double slash.

*Keyword* = *Value*

*Keyword* = *Value*//*Comment*

The possibilities and meanings of the keywords and values depend on the function that processes this data. The corresponding notes are contained in the file sections \[FILE INFO] and \[SECTION INFORMATION].

The comment is often used for a definition of the keyword when predefined keywords are used. For self-defined keywords or user variables, the comment should likewise be used for a description, as this significantly simplifies later editing.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/the-variable-system/editable-settings-files/structure-of-editable-settings-files-editing-in-the-general-text-editor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
