OpenBallistics desktop 0.1.22 (beta)

Units: metric/imperial per item, MOA+MIL side by side, pod range in yards

Setup -> Units picks distance, temperature, pressure, altitude, wind, velocity, energy and
target size units per screen (All metric / All imperial). Inputs keep the solver's units
underneath. Header MOA | MIL | BOTH splits the hold tiles. The station sends the range in
the picked distance unit to the pod and station OLED; the pod steps in yards.

OpenBallistics desktop 0.1.21 (beta)

OpenBallistics logo (reticle hub): logo files, app icons, headers, pod and station start screens

branding/make_logo.py builds every file from one geometry: SVGs (two-colour, light, one-colour cut, print-and-cut
sticker, horizontal with the name as outlines), PNGs and app icons, and 40 mm 2-colour STL / 3MF prints (plain and as a
badge). The apps use it in the header and as their icon; the pod's start-up screen and the station OLED draw it. The TP
Custom Rifle Parts logo stays on Setup -> About, in the desktop header and on its own OLED page.

OpenBallistics desktop 0.1.20 (beta)

Range stays put across screens; downloads use the Save dialog in the desktop app; no console windows on Windows

Range: screens only send their range / unit when their user changed it, and adopt the station's otherwise, so a stale
screen can't drag it back ('600 m from display'); the toast says whether the pod or another screen changed it.
Downloads: inside the desktop app the station page hands its CSVs / logs to the app, which shows the normal Save dialog
(Windows ignored the links, the Mac replaced the page). Windows: helper programs start without a console window.

OpenBallistics desktop 0.1.19 (beta)

Video overlay: newest shot takes over; a clip shows only its own shot, numbered as in the session

With shots closer together than the overlay lasts (time of flight + impact sound, ~10 s at 1528 m), the first shot's
overlay stayed up over the next ones. Now the newest started shot wins, clips draw only their shot, and SHOT n uses the
session's shot number.

OpenBallistics desktop 0.1.18 (beta)

Desktop app: trusted certificates for https in the packaged app (macOS update check failed)

The Python inside the Mac app has no CA list, so the update check (and the Pi OS download) failed with
CERTIFICATE_VERIFY_FAILED. The app now points SSL_CERT_FILE at certifi's bundle, and the self-test fails the build if
no certificates are loaded.

OpenBallistics desktop 0.1.17 (beta)

GoPro: pair in one bluetoothctl session (pairable, default agent, scanning) - the way that worked on the Pi

Tom's manual test showed pairing only succeeds with an interactive session: power on, pairable on, NoInputNoOutput
agent set as default, scan on, pair, then trust. The station now does exactly that, answers any yes/no question, and
leaves a camera BlueZ already has paired alone unless it refused commands.

OpenBallistics desktop 0.1.16 (beta)

GoPro: make the Pi's Bluetooth pairable while pairing (it was 'Pairable: no' -> AuthenticationFailed)

OpenBallistics desktop 0.1.15 (beta)

GoPro: pair properly with bluetoothctl when the camera refuses commands (ATT 0x0e)

A link that isn't really paired gets 'ATT error 0x0e (Unlikely Error)' on every write. New cameras, and any refusal
like that, now clear the old pairing and pair with bluetoothctl's NoInputNoOutput agent, then trust the camera.

OpenBallistics desktop 0.1.14 (beta)

Station Devices page: Bluetooth explorer on the Pi, C1 capture card; GoPro pairs automatically

The Sensors tab becomes Devices and gets the Bluetooth explorer (moved to openballistics/blescope.py, run on the
station's Bluetooth via /api/ble), so it works from the phone at the range and in the desktop Solver tab. With no
GoPro set up, the station now finds one in pairing mode and pairs it by itself (Pair automatically, on by default).

OpenBallistics desktop 0.1.13 (beta)

Desktop updater: note how builds are published