The button on the UI sends a message to radio thread for changing the print_raw_data flag.
I could have also done this differently by doing the following:
change the log message type from RNode to UI to differentiate logs from raw data.
do the filtering of whether raw bytes are printed or not on the UI side.
the RNode thread gets the values and sends them to the radio.
If the radio firmware accepts the values, a response is sent back. The response is then processed and the UI is updated.
So, the true test of whether a value took, is the radio sending back a resonse and seeing the label on the UI change.
Instead of having the main app handle it, now the handler is part of the class.
Also added a name to the SubmitEdit class, so a single handler can decide what widget activated the handler.
Renamed a bunch of functions to make it easier to follow.
Fixed a number of issues with duration command. We have to wait until rnode is initialized before staring to count seconds. Otherwise, the thread terminates before radio is full initialized.