Unit classes

Each project has its own cross-reference. When scanning the project, the cross-reference in a client project searches for uses of unit classes in the client project (in the design area), e.g. in the UnitClassName (Modern UI) property of the controls. The cross-reference of a server project searches for uses of unit classes in the server project, e.g. in the Unit class (display) and Unit class (process) parameters of the variables. In single projects, the client and server are combined so that there is only one cross-reference that performs both searches.

The cross-reference checks for each use whether the respective unit class has been defined and, conversely, whether a defined unit class has been used.

Figure 1: Responsibility of the respective cross-reference for client-server projects and single projects

Legend:

The analysis is performed by the cross-reference of the client project. The starting point of the arrow indicates the source of the definition, the tip of the arrow indicates the use of the definition.

The analysis is performed by the cross-reference of the server project. The starting point of the arrow indicates the source of the definition, the tip of the arrow indicates the use of the definition.

In a single project, there is only one cross-reference. The starting point of the arrow indicates the source of the definition, the tip of the arrow indicates the use of the definition.

After scanning the project, the results are displayed in a table in the Unit classes view in the Cross-reference node of the respective project.

The table contains the following columns:

Name

Specifies the name of the unit class.

Status

Indicates the status of use: either Correct, Warning or Error.

Status Description

Detailed information on the status.

Status Description	Description of the	Status
Correct	The use of the definition is error-free.	Correct
Defined, but no use found	The unit class has been defined but not used. Important: If the cross-reference is not used for a unit class, it does not mean that the definition is superfluous and can be deleted for the following reasons: The unit class may have been used in a variable that is bound to a control. The cross-reference of the client does not recognise this and marks the unit class as a warning. The unit class may have been used in the code, but in Modern UI and Web UI projects, code files(*.cs, *.vb, *.js) are not analysed by the cross-reference. In Classic U I projects, the cross-reference analyses the code files (*.cs, *.vb), but not all code constructs can be interpreted. If unit class names are only obtained at runtime, e.g. from a data source, then these unit classes cannot be recognised by the cross-reference. Before you delete a unit class, make sure that the unit class is not used in the variables (via the cross-reference of the server project), the unit class is not used in the code.	Warning
Used, but not defined	The unit class was used, but not defined in the project file. The units cannot be switched in the course of the application.	Error

System

The Variables entry means that the unit class is used in the Variables system module. If Designis specified, the definition in the design area is used.

Used in

Specifies the relative path of the form (Classic UI), view (Modern UI) or page (Web UI) where the right is used.

Source group, source, source detail

Further details on use