mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #853] Manually specifying a monitor as non-Apple display #537
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#537
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 @waydabber on GitHub (Dec 21, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/853
Discussed in https://github.com/MonitorControl/MonitorControl/discussions/852
Originally posted by qvacua December 21, 2021
I have the following setting: MacBook Pro (M1 Pro) with macOS 12.1 + LG UltraFine 4K 21.5" + Dell U2719D. Sometimes–I could not find out when exactly this happens–macOS recognizes the Dell monitor as brightness-controllable monitor, i.e. the Display settings or the Control Center shows a brightness slider for it. When I use the slider, the brightness of the LG monitor changes 😞.
MonitorControl thinks that the Dell monitor is an
model/AppleDisplaysince the system returns a value for the brightness (if I read the code correctly;DisplayManager.isAppleDisplay()). And it changes the brightness of the LG monitor when I use the slider for the Dell monitor (as expected).Would it be an option to include an option to "force" a monitor to be a
model/OtherDisplay? I've filed a bug at Apple, but I guess this won't be fixed...@stale[bot] commented on GitHub (Dec 21, 2022):
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.