Currently the {TIMEPLOT|DATA|... line uses a |T| as a time placeholder which is presumably populated with a timestamp at the time it is parsed within Megunolink. For slow data rates this isn't a problem, however for intermittently high data rates I have to buffer the data and then feed at a measured...

More information:
At 230400 the progress slider does not move at double the speed of 115200.
Instead it jumps around wildly. It looks like the baud rate is not being limited at all.

I'm using a data file I previously recorded. Playback at 115200 works fine. Doubling the baud rate to 23400 causes the plot to display nonsense and freeze. See attached picture. At 27:23 I increased the baud rate. No error messages are displayed. After disconnecting the source the plot displays more...

I'm sending about 200 messages per second to a plot and interface panel via MQTT. The plot is using the "general MQTT client" and the panel is using the "MQTT device network". At program startup it works fine. The plot is smooth and CPU usage is about 10% on a 3GHz I5 processor. ...

For example, I have a plot that needs to show the states of several on/off switches and motor speeds. The switches only have 2 states. I imagine a on/off timeline overlay on top of the speed graph that allows the switch states to be shown without overlapping each other.. Here is an example picture h...

For example, if no incoming data received within the last x seconds then throw up a warning dialog or provide some other indication to indicate that the displayed information may not reflect the current situation. My main concern is having an interface panel that displays old information due to loss...