Evan Black

Hey Charles, 1) The "dot" syntax for setting an attribute is an error with the documentation. It should be the "arrow" syntax, as you pointed out. I've corrected this in...

For the first thing, unfortunately, `OptionalValue` is a templated type, so you must pass the contained type in angle brackets, like this: ```cpp OptionalValue (2.0) // This part ^^^^^^^^ ```...

Hey Charles, The `Height` attribute tells the application to calculate a scale factor for the given model, so it ends up being the specified height. This performs a "uniform scale,"...

Hey Charles, I'm glad you were able to find what you needed. I've opened a new issue to add non-uniform scaling, as well as also allowing width or depth to...

Hey Charles, I did also consider expanding the `Scale` attribute similarly to the way you described here. It would have functioned similarly to the [`Orientation` property](https://github.com/usnistgov/NetSimulyzer-ns3-module/blob/master/doc/source/nodes.rst#attributes). However, I don't think...

The API break part I'm referring to would be in the module, specifically anything using the attribute (or the `NodeConfigurationHelper`) and not the setter function directly. ```cpp using netsimulyzer; auto...

Hey Charles, As far as output is concerned, this is how I thought to do it. For the 'scale' property ```jsonc [{ // Old style, produces a uniform scale "scale":...

Hey, the example that's failing there (the WiFI Bianchi one) fails because ns-3 has since changed the WiFi API. You should be able to remove that example from the `wscript`...

Edit: you'll need to remove the `obj.source = 'wifi-bianchi-netsimulyzer.cc` as well, here's the full snip-it again: ```python obj = bld.create_ns3_program('wifi-bianchi-netsimulyzer', ['netsimulyzer', 'core', 'mobility', 'network', 'wifi']) obj.source = 'wifi-bianchi-netsimulyzer.cc' ```

Hey Charles, We've definitely discussed this since I do agree it's hard to keep track of the current perspective. I was thinking of adding some sort of UI element like...