... | ... | @@ -23,7 +23,7 @@ Even though the zones defined by their respective tethering distances overlap, t |
|
|
|
|
|
By moving object **A** closer to object **B**, object **A** detects that a potentially **tetherable** object is within its tethering distance. Object **A** initiates the tethering process by perform a handshake with object **B** in order to find out whether it is ready and willing to be *tied* to object **A**. If this is the case, the link between the two objects will be established, visually shown by a **Tether** being displayed between the two objects. Objects **A** and **B** may be moved and the shown **Tether** will follow along as long as the relative distance between **A** and **B** is smaller than **A**'s tethering distance. If this distance is exceeded, then the Tether is *torn down* and both objects are no longer *tied* together.
|
|
|
|
|
|
It is important to note that tethering is not limited to tangible objects alone. [Coronas](authoring/coronas), [Markers](authoring/Markers) and even [Content](authoring/Content) may become potential tethering candidates, provided they implement the required interface.
|
|
|
It is important to note that tethering is not limited to tangible objects alone. [Coronas](authoring/coronas), [Markers](authoring/Markers) and even [Content](authoring/Content) may become potential tethering candidates, provided they implement the required [Tetherable](development/features/Tethering) interface.
|
|
|
|
|
|
## Tethers
|
|
|
As we have just seen, **Tether**'s take care of visually showing that two **tetherable** objects are tied together. But their purpose doesn't stop there. As you might have guessed, when establishing a connection between two objects, we're also establishing a kind of communication channel between the two objects, one of them *providing* information which is then *received* by the other. So **Tethers** in fact have a *direction*, with information flowing from the **providers** to the **receivers**. **Tethers** are defined in the [scenario's](authoring/Scenario) connections section.
|
... | ... | |