Module Interface IIntegratedVisualizer

Package: inet.visualizer.contract
File: src/inet/visualizer/contract/IIntegratedVisualizer.ned

This module interface allows configuring different IIntegratedVisualizer submodules from INI files. Integrated visualizers are compound modules, they don't display anything on their own. Instead they combine multiple visualizers, most often simple modules, to provide a convenient way to add complex visualizations to a simulation.

Usage diagram:

The following diagram shows usage relationships between types. Unresolved types are missing from the diagram.

Inheritance diagram:

The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.

Used in compound modules:

Name	Type	Description
IntegratedVisualizer	compound module	This module integrates canvas and osg visualizers into a single module.

Networks:

Name	Type	Description
ComplexConfiguratorNetwork	network	(no description)
Crosstalk	network	(no description)
DynamicRadioNetwork	network	(no description)
ErrorRateTest	network	(no description)
HandoverNetwork	network	(no description)
Lan80211	network	(no description)
Layered80211	network	(no description)
LayeredAPSK	network	(no description)
MultiRadio	network	(no description)
Net	network	(no description)
Net80211	network	(no description)
ObstacleTest	network	(no description)
PowerNetwork	network	(no description)
Scenario	network	(no description)
Synchronized	network	(no description)
TestNic	network	(no description)
TestRadioScaling	network	(no description)
Throughput	network	(no description)
Throughput	network	(no description)
WiredAndWirelessHostsWithAP	network	(no description)
WirelessA	network	(no description)
WirelessNetWith2DHCP	network	(no description)

Properties:

Name	Value	Description
display	i=block/app_s

Source code:

//
// This module interface allows configuring different ~IIntegratedVisualizer
// submodules from INI files. Integrated visualizers are compound modules, they
// don't display anything on their own. Instead they combine multiple
// visualizers, most often simple modules, to provide a convenient way to add
// complex visualizations to a simulation.
//
// @see ~IntegratedCanvasVisualizer, ~IntegratedOsgVisualizer, ~IntegratedVisualizer
//
moduleinterface IIntegratedVisualizer
{
    parameters:
        @display("i=block/app_s");
}