mirror of
https://github.com/MarekZegare4/MeshCore-Solo.git
synced 2026-09-14 15:16:40 +00:00
fix(ui): message bubble color, received-message hop count, list wrap-around, age fallback; add sim WASM build workflow
- Unselected message bubbles no longer carry a stray light-filled header strip behind the sender name -- the one place with a filled patch on an otherwise plain row. Selected fill is unchanged. - Received DMs and channel posts now show their hop count as the same tiny digit icon a sent message already uses for its repeater/echo count, using the hop path the mesh already records for incoming messages. - DM/channel history list: UP at the oldest message now wraps straight to the newest (not the compose row), closing the loop the same way every other list in the UI does at its ends. - A received message's age no longer goes blank when its timestamp reads slightly ahead of the device's own clock (sender/receiver skew, or an unsynced receiver) or is genuinely unknown -- both now show the receipt time instead of leaving the row with just a name and hop count. - release-notes.md: add the v1.28 section covering the above plus this cycle's already-committed dev fixes (GPS altitude field, units compliance, noise floor, Msg wake location, bot relay tracking, PR #34). - Add .github/workflows/build-solo-sim.yml: builds the companion+repeater WASM sim via Emscripten and attaches it as a fixed-name asset to the tag's draft release, independent of the hardware firmware build job. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,3 +1,23 @@
|
||||
## MeshCore Solo Companion Firmware v1.28
|
||||
|
||||
### What's new
|
||||
|
||||
- **The Clock/Lock dashboard gets a separate "Altitude (GPS)" field**, alongside the existing barometric one (now labelled "Altitude (Baro)") — the original single Altitude field only ever read a barometric sensor's telemetry, showing `--` on any board without one even with a perfectly good GPS fix.
|
||||
- **Received messages now show how many hops they actually took to reach you**, right in the message list — the same tiny digit-icon a sent message already uses for its repeater/echo count, now shown for incoming DMs and channel posts too, using the hop path the mesh already records for them.
|
||||
|
||||
### Fixes
|
||||
|
||||
- **Every altitude reading (baro + GPS, Clock and Lock screen) and the GPS home page's "alt" row now respect Settings › System › Units**, same as every other distance in the UI — none of them checked metric/imperial before. Locator's Radius row had the same gap and is fixed the same way.
|
||||
- **The Radio home page's noise floor showed "n/a" whenever Pwr save (RX duty-cycle) was on**, on the assumption duty-cycle RX can't sample it. That's stale — the radio already recalibrates it periodically even under duty-cycle, which is why Diagnostics' own reading was already showing something real. Radio home page now matches.
|
||||
- **"Msg wake" moved from Settings › Sound to Settings › Display** — a more logical home for a display-wake toggle than notifications. Menu order only; the setting itself is unaffected.
|
||||
- **Remote Bot's channel replies (trigger reply, channel command reply, `!gps` fix result) never showed which repeaters echoed them back**, unlike every other way of posting to a channel. Bot-originated posts now arm the same relay tracking an app or on-device send already gets.
|
||||
- **Creating a new message channel didn't refresh the channel list until leaving and re-entering the screen.** Contributed by @3urobeat.
|
||||
- **The DM and channel history lists didn't wrap at their ends like every other list in the UI.** UP at the oldest message now wraps straight to the newest, and DOWN past the newest wraps to the compose row and back to the oldest, closing the loop both ways.
|
||||
- **Unselected message bubbles had a stray light-filled header strip behind the sender name**, the one place in the UI with a filled patch on an otherwise plain row. Unselected bubbles are now plain (matching every other unselected row); the selected fill is unchanged.
|
||||
- **A received message could show no time at all — just the sender name and hop count** — whenever its timestamp read slightly ahead of the device's own clock (sender/receiver clock skew, or the receiver's clock not synced yet) or was genuinely unknown. Both cases now show the receipt time instead of going blank.
|
||||
|
||||
---
|
||||
|
||||
## MeshCore Solo Companion Firmware v1.27
|
||||
|
||||
### What's new
|
||||
|
||||
Reference in New Issue
Block a user