... | ... | @@ -8,3 +8,33 @@ |
|
|
<figcaption>Fig. 1 - Marker Properties</figcaption>
|
|
|
</figure>
|
|
|
</div>
|
|
|
## Type
|
|
|
The **mandatory** **`<type>`** tag allows specifying the kind of marker to be instantiated. Markers are identified by their Java Class name. For instance, the following snippet would specify to use a marker defined by the Java **ModalMarker** class:
|
|
|
|
|
|
```xml
|
|
|
<type>ModalMarker</type>
|
|
|
```
|
|
|
## Name
|
|
|
The **optional** **`<name>`** tag allows specifying a given name for the widget.
|
|
|
|
|
|
```xml
|
|
|
<name>The Moon</name>
|
|
|
```
|
|
|
|
|
|
## Handles
|
|
|
Each Marker must be identified by at least one unique Handle.However, you may specify multiple markers should the necessity arise. Each marker definition requires its own `<handle>` tag definition within the overall `<handles>` group of tags. The following snippet assigns the id **30** to the enclosing marker definition:
|
|
|
|
|
|
```xml
|
|
|
<handles>
|
|
|
<handle>30</handle>
|
|
|
</handles>
|
|
|
```
|
|
|
|
|
|
## StageId
|
|
|
The **optional** **`<stageId>`** tag determines on which stage the marker will appear. If not specified, the marker will appear on the stage representing the tangible table itself, which by definition has the **`<stageId>`** 0 (zero). When specified, it is important to make sure the referenced stage was previously declared at [Scenario](authoring/scenario) level in the **`<StageSet>`** section.
|
|
|
|
|
|
## Stage Position
|
|
|
The **optional** **`<stagePosition>`** tag determines the spatial position of the marker on the given stage. The spatial position is expressed as a point following the TULIP convention. Have a look at the section about [common point properties](authoring/Point) for more information about how to define a point in TULIP scenarios.
|
|
|
|
|
|
## Coronas
|
|
|
As **Markers** are similar to [Widgets](authoring/objects), they also do implement the functional side of the entity they should represent, whereas their visual representation id handled by dedicated objects called **Coronas**. The `<coronas>` tag groups individual `<corona>` definitions for a given Marker. [Coronas](authoring/coronas) will be covered separately. |
|
|
\ No newline at end of file |