With arrow annotations you can point to a particular project member or a member group. The arrow annotation is used often together with the legend and group annotations. As such the annotations are very useful for foreigner developers to understand the structure of your implementation. Group annotation members appear in Composer as gray pointers (arrows):

The annotations have no effect on the application itself. They exist for descriptive purpose only. Annotations can be used everywhere within your project.

Unlike other members, annotations are not inherited when you derive a new class from a base class containing annotations. The annotations from the base class are simply ignored.

Adding a new annotation member.

The name of the annotation member has no effect on the function of your application. However, it has to be unique in its particular context.

You can create any number of copies of an already existing annotation member.

The following table shows the complete list of attributes provided by the arrow annotation member:

Attribute name	Short description
Point1	Determines the start position of an annotation arrow member.
Point2	Determines the end position of an annotation arrow member.

This section describes the Chora syntax of how annotations are stored inside Embedded Wizard project files. The knowledge about the syntax can be helpful when you plan to process the project contents by third party tools. In particular, the general purpose Export and Import functionality introduced in version 14 requires a good understanding of how project members are represented in Chora syntax to correctly interpret the exported members and synthesize the Chora code for members to import. Please note, Embedded Wizard project files (and thus Chora code) are encoded as text in UTF-8 format.

In Chora syntax, annotation arrow definition is always introduced with the keywords note arrow, followed by the name of the annotation member and a list of initialization values for member's own attributes. The attributes are enclosed between a pair of curly braces {..}, whereby each attribute starts with the keyword attr followed by the name of the affected attribute, an assignment operator =, the assigned value and ; semicolon sign. Wherever necessary, the tokens are separated by whitespace signs. In case of the annotation arrow member, only the attributes Point1 and Point2 are supported. The following example demonstrates the described syntax:

Each Chora file (or text exchanged with an external Export and/or Import tool) can be (or even should be) prefixed with $version directive. This directive determines the version number of the included Chora code. For details concerning the syntax of the version please see the chapter $version macro. Furthermore, the code can include a $scope directive followed by a path to a project member acting as the original owner of the corresponding code. That means the members described by the Chora code existed inside the member specified in $scope.