Add Software Marker Widget

[retiutut]

Closes #1091 Closes #1114

Account for the following:

• [x] Insert markers using clickable buttons
• [x] Have multiple markers (e.g. 1.0, 2.0, etc)
• [x] Insert markers using keyboard shortcuts (even when widget is closed)
• [x] Print marker and timestamp to console log
• [x] Time series graph to show markers over time (live and playback)
• [x] Networking Widget output
• [x] UDP marker receiver and UI in the widget #1114

---

Other consequential changes while reviewing keyboard shortcuts:

• remove s shortcut to Stop Streaming
• remove b shortcut to Start Streaming
• remove d shortcut as it was unused (it used to be for Cyton to reset board to defaults, this would not sync with ADS1299 settings UI) All of the above shortcuts are no longer useful or could cause issues if accidently pressed. We can still start/stop streaming using spacebar.

[retiutut]

Markers making their way into OpenBCI CSV files. Loaded into spreadsheet and sorted that column. You can see the markers next to the timestamp channel.

[retiutut]

We will print an approximate time that a marker was inserted into the data. Here we see that the timestamp was correct down to the millisecond!

During this test, only one marker was inserted, so this screenshot/data is not an accident.

[retiutut]

Markers showing up in playback!

[retiutut]

LSL Networking Test

UDP Networking Test (everything is right but the sampling rate calculation is incorrect)

OSC Networking Test

Serial Networking Test

[retiutut]

• [ ] Add some padding on the right side of the buttons
• [x] Consider making the buttons larger and splitting them into two rows
• [ ] Autoscale the height of the graph

I don't think autoscaling is the way to go here (for now), until users are allowed to stream in floats from another program. Then, it should be the only option for that source.

[retiutut]

Successfully inserting markers (as floats) from external process over UDP.

[retiutut]

[philippitts]

• [ ] Add some padding on the right side of the buttons
• [x] Consider making the buttons larger and splitting them into two rows
• [ ] Autoscale the height of the graph

I don't think autoscaling is the way to go here (for now), until users are allowed to stream in floats from another program. Then, it should be the only option for that source.

Maybe we should add it now that it's possible to stream in floats from an external source?

[retiutut]

• [ ] Add some padding on the right side of the buttons
• [x] Consider making the buttons larger and splitting them into two rows
• [ ] Autoscale the height of the graph

I don't think autoscaling is the way to go here (for now), until users are allowed to stream in floats from another program. Then, it should be the only option for that source.

Maybe we should add it now that it's possible to stream in floats from an external source?

Instead of this, users now have full control over the Y Axis, up to 20.0. Autoscale is kind of weird here since all values should be greater than 0, and it may cause "bouncing" when the graph resizes. Overall, the UX is likely better without the Y axis dynamically changing.

EDIT: On second thought, users should have the freedom to send values > 20 and still see it, though it might look weird when the graph Y axis jumps from lets say 1000 to 1 after the data point leaves the graph.

I'll add Auto as an option to Vert Scale, since we have a precedent in other widgets.

• [x] Add autoscale option to vert scale dropdown

[retiutut]

• [x] It looks like there a few files where the whole file ended up as a diff for some reason. Can you double check your line endings and try restaging the files?
• [ ] I'm not sure how to provide external triggers via something like netcat. Can you provide some information (PR comment is fine) on this? Should the external process listen or host the connection? Does the stream have to be started first?

In the included Python example in NetworkingTestScripts folder, we send a single float over UDP to the specified IP and Port. Though, the float is packed as a byte array.

The GUI will always listen on the specified port, and this does not use multicast. When the IP and Port are changed, the GUI will remake the UDP listener after leaving the textfield or pressing enter. A message will show at the bottom of the GUI and console log. This means the GUI and external process are completely independent and either can be started at any time.