Skip to content

Hide status bar dots for unsupported optional sections#2412

Merged
ten9876 merged 1 commit into
aethersdr:mainfrom
rfoust:codex/fix-status-bar-dots
May 7, 2026
Merged

Hide status bar dots for unsupported optional sections#2412
ten9876 merged 1 commit into
aethersdr:mainfrom
rfoust:codex/fix-status-bar-dots

Conversation

@rfoust

@rfoust rfoust commented May 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Hide the TGXL and PGXL status bar separator dots when their optional indicators are hidden.
  • Keep separator styling and spacing unchanged by creating the optional separators through the same addSep() helper as the existing fixed separators.
  • Toggle each optional separator together with its matching indicator when TGXL/PGXL presence changes after connection, and clear both again on disconnect.

Bug Fixed

On radios or configurations where optional status bar sections such as TGXL or PGXL are unsupported or not present, the indicators are hidden but their dot separators remained visible. That could leave multiple dots in a row in the bottom status bar.

Testing

  • cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=RelWithDebInfo
  • cmake --build build -j8

Copilot AI review requested due to automatic review settings May 6, 2026 14:32
@rfoust rfoust requested a review from ten9876 as a code owner May 6, 2026 14:32

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a UI glitch in the bottom status bar where separator dots (“·”) could remain visible even when optional sections (TGXL/PGXL) are hidden, resulting in multiple dots in a row on radios/configs without those peripherals.

Changes:

  • Adds dedicated separator QLabels for the TGXL and PGXL optional status sections and initializes them hidden.
  • Updates the TGXL/PGXL presence change handlers to toggle both the indicator and its matching separator together.
  • Clears both optional indicators and separators on disconnect to keep the status bar consistent across reconnects.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/gui/MainWindow.h Adds member pointers for TGXL/PGXL separator labels so they can be toggled alongside the indicators.
src/gui/MainWindow.cpp Makes addSep() return the created separator, wires optional separators to presence/connection state, and initializes them hidden to avoid stray dots.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@aethersdr-agent

Copy link
Copy Markdown
Contributor

Hi @rfoust — thanks for the contribution! Just took a look at the failing check on 98f6f05, and the news is good: this isn't your code.

What failed

Only one check went red:

  • Cleanup artifacts job → Delete artifacts step (run)

That's an infrastructure-side housekeeping job that runs after the build pipeline and calls the GitHub Artifacts API to remove transient build outputs. It's not part of compile/test/lint — those all live in the build, Agent, analyze (cpp), and check-windows jobs, and the ones that have completed (Agent, Upload results, Prepare, check-paths) are all green. build and analyze (cpp) were still running when I checked.

Why this is a CI infrastructure issue, not your diff

Your change is scoped to src/gui/MainWindow.cpp and src/gui/MainWindow.h — adding m_tgxlSeparator / m_pgxlSeparator QLabel* members and toggling their visibility alongside the existing m_tgxlIndicator / m_pgxlIndicator so the · separator chars don't dangle when TGXL/PGXL aren't present. Nice, surgical UI fix. There's no path by which that touches the artifact-deletion workflow.

The Delete artifacts step typically fails on transient GitHub API glitches — rate limits, eventual-consistency on artifact IDs that were just uploaded, or 5xx responses from actions/artifacts. It's a known-flaky class of failure across many GitHub Actions setups.

What to do

Nothing on your end. A maintainer can re-run the failed job (or it'll naturally resolve on the next push); the cleanup job's failure does not block merge in this repo's policy. If you want to give the pipeline a nudge, an empty commit or a push of any tweak will retrigger.

Thanks again for the polish — those orphaned · separators have been a small papercut. 🙏

@ten9876 ten9876 merged commit ac9add1 into aethersdr:main May 7, 2026
8 of 9 checks passed
@ten9876

ten9876 commented May 7, 2026

Copy link
Copy Markdown
Collaborator

Claude here — thanks for the clean fix, Robbie! Caught a real visual nit and the symmetric toggling on every visibility path keeps it from drifting. Merged as ac9add1.

73, Jeremy KK7GWY & Claude (AI dev partner)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants