You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Heads-up: LumaGlass fork (likaia/MonitorControl) has missing source file for its Tahoe HUD fix #1890
Context: #1782 points people to the LumaGlass fork (likaia/MonitorControl) as a possible workaround for the missing Tahoe OSD slider. That issue is now locked and likaia's repo has Issues/Discussions disabled, so posting here instead.
Looked into LumaGlass as a candidate fix. Found a problem: MonitorControl/Support/BrightnessHUDController.swift is referenced in project.pbxproj (Sources build phase, AB10C000.../AB10C001...) but the file itself doesn't exist in any commit on any branch of that repo:
git log --all --diff-filter=A --name-only | grep -i hud
→ only CUSTOM_BRIGHTNESS_HUD_PLAN.md, no .swift file
Likely cause: the fork's .gitignore contains a large templated block (looks like a Jenkins-home template) with a root-level blanket /* ignore + whitelist exceptions, around line ~4670. It appears to silently match and exclude this new root-level Swift file:
The fork doesn't build from source as committed (missing-file compile error).
The actual implementation of the macOS 26 HUD fix — the fork's main feature — isn't in the public source, only in the prebuilt DMG/ZIP release assets linked from the GitHub release. Can't be reviewed/audited from the repo alone.
Rest of the diff against upstream (MenuHandler/SliderHandler UI rewrite, Sparkle feed repoint, MediaKeyTap dependency swap) checked out fine — no risky APIs, no entitlement changes, dependency fork is byte-identical to MonitorControl's own MediaKeyTap fork. This missing file is the one open concern.
@likaia — flagging in case you want to fix the .gitignore/commit the missing file. Mainly posting here for visibility since the fork's own issue tracker is closed and #1782 is locked.
#1728 was converted to #1873, so the discussion can go on there.
For macOS Golden Gate 27 there is now a way to access the native Control Center UI, so I'll probably add that as an option (I added this as an option for BetterDisplay v5.x on macOS 27 as well). For Tahoe the workaround here is probably acceptable (#1873 (comment)), at least if the other alternative is adding and managing an entirely custom HUD trying to replicate the native look&feel. I did this for BetterDisplay but that requires constant tweaking and follow-up (and there are slight differences still) as Apple does tweak the native appearance itself from time-to-time.
Activity
waydabber commentedon Aug 11, 2026
#1728 was converted to #1873, so the discussion can go on there.
For macOS Golden Gate 27 there is now a way to access the native Control Center UI, so I'll probably add that as an option (I added this as an option for BetterDisplay v5.x on macOS 27 as well). For Tahoe the workaround here is probably acceptable (#1873 (comment)), at least if the other alternative is adding and managing an entirely custom HUD trying to replicate the native look&feel. I did this for BetterDisplay but that requires constant tweaking and follow-up (and there are slight differences still) as Apple does tweak the native appearance itself from time-to-time.