Evan Black
Evan Black
Several people have requested the ability to change the 3D model of a node while the simulation is running, like the color
The `OptionalValue` class does not work with ns3's `ConfigStore`, since that requires the ability to serialize/deserialize from strings, and we don't support that operation. Look into either writing specific implementations...
Add a callback & corresponding event to the `NodeConfiguration` class to indicate the Node has begun to transmit. This event controls the display of a "bubble" in the application. Potentially...
It's somewhat inconvenient when assigning values to optional attributes to type out the full, templated type. This also causes confusion when assigning those attributes, as it may not be easy...
To get an accurate picture of the network a `Node` is connected to, we must also collect from the `Channel`. Configure the channel once a configured `NetDevice` is attached to...
In order to do things like displaying wired links between `ns3::Node`s, we must first be able to identify and track `NetDevice`s. Add the following components to the module: ## `NetDeviceConfiguration`...
Automatic formatting does not seem to play well with the attribute blocks. It's critical those sections be clear as it's very likely a user will end up reading them. Go...
`CategoryAxis::ValuePair::key` is referred to as an ID for a given state the documentation, so update the name to reflect that usage
`ValueAxis` only uses numbers for values, so I think `NumericAxis` conveys that a bit better. Rename both module elements & output elements. The issue in the application: https://github.com/usnistgov/ns3-visualizer3d/issues/17