Skip to content

Say what was measured about the hidden icon, not what was inferred - #3

Merged
TerrifiedBug merged 2 commits into
mainfrom
fix/menubar-comment-precision
Aug 14, 2026
Merged

Say what was measured about the hidden icon, not what was inferred#3
TerrifiedBug merged 2 commits into
mainfrom
fix/menubar-comment-precision

Conversation

@TerrifiedBug

Copy link
Copy Markdown
Owner

Follow-up to #2, documentation only. Four corrections, each replacing something I could not back with a measurement.

  1. An inference stated as measurement. The comment claimed that placing the icon under one identity leaves it unplaced under the other. Never tested. The mechanism that was measured is the self-sustaining loop: both identity keys (yap:Item-0 and com.terrifiedbug.yap:Item-0) sat in Thaw's hidden section, and with "new items appear in hidden" set, an item it has no section for is cmd-dragged there — AppKit then persists that drag as yap's own saved position, which I watched go from 430 to 5518. That is why it came back hidden on every launch.

  2. A claim about Thaw's relaunch tracking. "Matches on bundle identifier, recognises only the bundled one" came from reading one function and generalising. The measurement contradicts the generalisation: Thaw persisted the yap:Item-0 fallback key in its saved layout alongside the bundled one. Clause deleted; the two identities and the loop above carry the comment on their own.

  3. The exec-failure note was wrong. It said yap "cannot hold a place in the menu bar" without an identity. It can: the embedded __TEXT,__info_plist gives the process a preferences domain whatever path it was started from, so NSStatusItem Preferred Position still persists. What it falls back to is the process-name identity LaunchServices hands out — the pre-Run the daemon from inside the app bundle so the icon keeps its place #2 behaviour.

  4. The README instruction did not work as written. It told people to drag the mark out of the manager's hidden section. macOS needs Command held to move a menu bar item, and the section has to be revealed first. Now says both.

Gate: release build, the CI smoke steps, the embedded-plist check, and swiftlint at 75 violations — same as main.

Three corrections to the comments and README that shipped with the last
change.

The claim that placing the icon under one identity leaves it unplaced
under the other was an inference, never tested. What was measured is the
loop that keeps it hidden: both identity keys sat in Thaw's hidden
section, and with "new items appear in hidden" set, an item it has no
section for is cmd-dragged there and AppKit persists the drag as our own
saved position — 430 rewritten to 5518.

The exec-failure note said yap "cannot hold a place in the menu bar"
without an identity. It can: the embedded __TEXT,__info_plist gives it a
preferences domain either way, so a position still persists. What it
falls back to is the process-name identity LaunchServices hands out,
which is what it had before.

The README told people to drag the mark out of the hidden section, which
does not work as written: macOS needs Command held to move a menu bar
item, and the section has to be revealed first.
Sourced from one function that matches on bundle identifier, then
generalised into 'recognises only the bundled one' — which the measurement
contradicts: Thaw persisted the yap:Item-0 fallback key in its saved
layout alongside the bundled one. The two identities and the hidden-section
loop are the measured facts and they carry the comment on their own.
@TerrifiedBug
TerrifiedBug merged commit 8f6d137 into main Aug 14, 2026
1 check passed
@TerrifiedBug
TerrifiedBug deleted the fix/menubar-comment-precision branch August 14, 2026 18:06
@TerrifiedBug TerrifiedBug mentioned this pull request Aug 14, 2026
Merged
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.

1 participant