mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1853] macOS 26 compatibility notes and reference implementation #1014
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#1014
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @likaia on GitHub (Apr 5, 2026).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1853
Before opening the issue, have you...?
Discussion
Hi, thanks for maintaining MonitorControl.
I have been testing the app on macOS 26 and ran into a few compatibility issues, mainly around menu presentation and brightness feedback behavior.
In my local fork, I adapted a few areas to make the app behave better on macOS 26, including:
I’m sharing this mainly as a compatibility note in case it is helpful to other users testing on macOS 26, and also in case any of the implementation ideas are useful upstream.
If helpful, I can summarize the changes in a more upstream-friendly way or split parts of them into smaller PR-friendly pieces.
Fork:
https://github.com/likaia/MonitorControl
Thanks again for the project.
@waydabber commented on GitHub (Apr 5, 2026):
Hi @likaia - it's nice to have MonitorControl forks. But the versioning (v1.1.0) and naming may confuse some - if the app is meant to have a separate life and feature set, maybe it would be better call it something else than MonitorControl (MonitorCommander or MonitorControlExtra etc, anything you like, just to differentiate) - you can of course mention it is "based on MonitorControl" if you wish. But it's just a suggestion, not a requirement of course.