... | ... | @@ -24,15 +24,18 @@ The optional **`<name>`** tag allows specifying a given name for the widget. |
|
|
```
|
|
|
|
|
|
## 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:
|
|
|
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>
|
|
|
```
|
|
|
## clusterable
|
|
|
As we have learned earlier, **Markers** are basically a kind of stationary version of [Widgets](authoring/objects). Their position is not directly controlled by the user but is governed by some external influence, for instance spatial data. The optional **`<clusterable>`** flag allows flagging this marker as being ready to be *clustered* in case multiple Markers would be too close to be distinguishable. Please bear in mind that **Markers** don't implement a clustering algorithm by themselves. This flag is merely an indicator that a marker *accepts* being clustered.
|
|
|
## Clusterable
|
|
|
As we have learned earlier, **Markers** are basically a kind of stationary version of [Widgets](authoring/objects). Their position is not directly controlled by the user but is governed by some external influence, for instance spatial data. The optional **`<clusterable>`** flag allows flagging this marker as being ready to be *clustered* in case multiple **Markers** would be too close to each other to be distinguishable. Please bear in mind that **Markers** don't implement a clustering algorithm by themselves. This flag is merely an indicator that a **Marker** *accepts* being clustered.
|
|
|
|
|
|
## Touchable
|
|
|
The optional **`<touchable>`** flag signalises whether this marker instance is interested in intercepting [touch events](development/features/Touchable) or not.
|
|
|
|
|
|
## 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.
|
... | ... | |