- if a request is re-used within a given time frame (<= the update
interval), this leads to incorrect event duplication and, thus, too
frequent listener calls

fixed nondeterministic behavior in SocialTransitionStrategy

Fixes: The usage of Collections.shuffle() and non-ordered HashSets in social movement led to different movement patterns each time the simulation was executed.

See merge request !36

- onClick events are now handled globally on the WORLD-panel
(significant boost in performance of the visualization)
- clicked (active) hosts are now more clearly visualized
- removed default host visualization for the sake of full customization.
However, we will provide a simple "showHosts" configuration option for
basic underlay visualization stuff in a later version of the
VisualizationTopologyView
- removed outdated and no longer used Components

- set target for movement currently only supported in the modularosm
model, feel free to extend other models by overwriting the default
implementation and create the corresponding merge requests.

Topology fix

Fixes bugs in DefaultTopologyComponent **recalculateLocalView()**:
It now returns a copy of the current position.
Also fixed a bug where it tries to generate edges to nodes not in the graph.

See merge request !32

removed previous 'fix' to AbstractTopology

PositionVector

- support for in-model placement of nodes

- deprecated MovementSupported
- used LocationSensor and LocationActuator
- decoupled nested listener structures used within the old models

actually changed.

implemented by all netlayers
updates MaxPeerCountChurnGenerator to support the interface (default
behavior still triggers the network-layer functions)

Fixed minor error in PositionVector for Lat = Y and Long = X.



See merge request !29

JSON Placement for OSM Data

Added a Placement Model for Hosts that takes OSM Input data for real map placement of e.g. infrastructure entities such as AccessPoints at "attraction point" locations.

See merge request !28

fix transition strategy to only fire once an Attraction Point is reached
remove POI limitation for Json-based Attraction Points