With the set member you can add a user-defined set data type consisting of uniquely named enumerators. Once defined, this data type can serve in the declaration of any data member within your project. At the runtime, the affected data member can assume any combination of the enumerators listed within the corresponding set member. Set members are represented in Composer by following bricks:

Please note, a set member can exist only within a unit member. Moreover, the maximum number of enumerators within a single set member is strictly limited to 32.

Adding a new set member.

Set members have a global character - they can be accessed from everywhere within your project. To address a set member, you must always use its full name, which is composed of the unit name, the member is defined inside, and the name of the member itself, both separated by :: (double colon) signs. For example Views::TextAlignment.

Every set member can contain up to 32 enumerator members. To add a new or edit existing enumerators open the set member in a new Composer page:

Please note, newly added set members contain already few dummy enumerators called per default FirstItem, SecondItem and so far. Feel free to rename or delete them.

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

You can also Drag & Drop a set member from the Browser into the Composer window and create so a duplicate of the affected member:

Duplicating a set by simply Drag & Drop it between the Browser and Composer windows

Every set member represents an individual user defined set data type, you can use in the declaration of variables, properties, arrays, local variables, local arrays as well as in parameter and return type declaration of a method. The set data type corresponds to the full name of the set member, composed of the unit name, the member is defined inside, and the name of the member itself, both separated by :: (double colon) signs. For example:

The name of the set member can be used within Chora expressions to form a literal of the corresponding set data type. The literal is composed of the corresponding data type name and a list of , (comma) separated enumerator names enclosed between a pair of [...] (square brackets). For example:

With the attribute Generator you can selectively control, whether the set member should be taken in account during the code generation or not. Configuring this attribute with the value false will exclude the member from your project unless the member name is explicitly involved within a Chora expression or data member declaration.

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

Attribute name	Short description
Brick	Determines the position and the size of a set member brick within the Composer window.
Description	Contains the description for the set member.
Generator	Controls the code generation for the affected set member.

This section describes the Chora syntax of how sets 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, set definition is always introduced with the keyword set, followed by the name of the set and a list of set items enclosed between a pair of curly braces {..}. Concerning the syntax of an item, please see Chora syntax of an item.

The definition of the set can be initiated by a comment block providing optional description for the set. The content of this comment corresponds to the value of the set's attribute Description. Furthermore the directives $rect and $output can be specified providing values for the corresponding attributes Brick and Generator. 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. In case of a set, $scope would specify the name of the unit the set belongs to.