Tony Collen

> So if the cursor is over the spectrum it should drop the marker where the cursor is or have you not implemented that yet? I haven't decided on this...

Yeah, although my guess is they are reading the actual analog meter values, i.e. what get sent through the meter port on the back. The radio only sends digital data...

I'm not sure what caused me to see this, but I'm actually getting them now that I've changed branches locally a couple times. On the radar, at least.

There seems to be a crash+restart when switching from CW to SSB, and then adjusting menu 6-11 from `High & Low Cut` to `Shift & Width`: ``` [info] TIMER: Update...

I think the band scope edges are actually working fine, but I encountered this while testing it out. So the title of this ticket might actually change. The crash isn't...

The cause of the problem is really annoying: the radio sends the filter info (hi/shift, low/width) BEFORE sending the message that the menu item changed, so open890 doesn't yet realize...

Encountered another one today while working on UI stuff. Mostly just leaving here for my own records: ``` [error] GenServer {:radio_connection_registry, {:tcp, "903e7dd4-38b7-4466-b48a-6b95b144ae44"}} terminating ** (ArithmeticError) bad argument in arithmetic...

The problem here is that when the menu item changes (`EX00611 001`), the radio sends filter info down _first_, but not the reply that the menu item actually changed. The...

The problem is that you have to know what the menu setting is to properly interpret the "lo/width" and "hi/shift" messages. So, here's what happens when sending the command to...

Noted - this will require reading the defaults for A, B and C, and storing them somewhere. Unfortunately there is no FIL CLR command to simply reset the current filter.