[GH-ISSUE #1853] macOS 26 compatibility notes and reference implementation #1014

Closed
opened 2026-05-05 07:01:48 -06:00 by gitea-mirror · 1 comment
Owner

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...?

  • Searched for existing issues

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:

  • updated menu layout/presentation for macOS 26
  • a custom native-style brightness HUD fallback for macOS 26
  • improved menu slider interaction on macOS 26

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.

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...? - [x] Searched for existing issues ### 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: - updated menu layout/presentation for macOS 26 - a custom native-style brightness HUD fallback for macOS 26 - improved menu slider interaction on macOS 26 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.
Author
Owner

@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.

<!-- gh-comment-id:4188980627 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#1014
No description provided.