Radio Operations Console v2.9.0

What works differently:

• Traffic on a check-in can now be followed through, on any net: select
  the check-in to record it passed to whom and how (say, by JS8Call or
  RTTY), an attempt that failed, or that it couldn't be passed, the same
  way a relay station does. Logging a check-in with traffic is unchanged,
  and ticking Handled is still all it takes; the rest is there only when
  you want it.
• Handled means passed on. Traffic marked Couldn't pass stays unticked,
  and the end-of-net warning still counts it.
• The ICS 309 has more lines: traffic passed on to a named station, each
  failed attempt, and traffic that couldn't be passed. A message passed on
  ends with how it went ("… (via RTTY)"). This applies to relay stations
  too, so the forms you send will look different.

This upgrade changes the database: traffic already on check-ins is moved
over, handled traffic recorded as passed when it was marked. A copy of the
database is saved before the upgrade; 2.8.0 can't open the upgraded data.

Added

• Where a check-in's traffic went. Selecting a check-in with traffic
  shows it with Passed…, Attempt failed… and Couldn't pass…. Its row
  then says where it went ("→ EOC via RTTY"), that it wasn't passed, or how
  many attempts failed. The ICS 309 and ICS 214 include it, and a net's
  Exports & forms has its traffic as CSV.
• HF conditions on the Weather tab, from NOAA's Space Weather
  Prediction Center: solar flux and the K and A indexes on one line when
  it's quiet, each with a word for what it means ("137 good", "K 2
  quiet") and a line more on hovering. When it isn't, it says what's
  happening in plain words (a radio blackout, a geomagnetic storm),
  whether HF is being absorbed at your area during a flare and for how
  long, and any storm forecast for the next couple of days. Checked every
  15 minutes while the tab is open.
• JS8Call, RTTY, PSK31 and FT8 are offered as ways traffic was passed.

Changed

• The ICS 309 says how traffic was passed, and what couldn't be. A
  message passed on ends with how it went ("… (via RTTY)"), and one given
  up on gets its own line ("Not passed to EOC: no path"), for relay
  stations as well as nets.

Download

See the assets below for your platform:

• Linux: .deb (Debian/Ubuntu), .rpm (Fedora/RHEL), or .AppImage (runs on most distributions)
• Windows: .msi or the .exe (NSIS) installer
• macOS: .dmg (one universal build, works on Apple Silicon and Intel)

Windows, Linux, and macOS builds come from the same source. Windows installers are not code-signed,
so Windows may warn ("Unknown publisher" / SmartScreen) before you can run one; macOS is not
notarized, so it may warn that the developer can't be verified (right-click the app and choose
Open to run it anyway). Neither is a sign of tampering, just the cost of an unsigned open-source
build.