mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #762] Better support for BetterDummy + Sidecar, Airplay or DisplayLink #494
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#494
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 (Nov 2, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/762
Originally assigned to: @waydabber on GitHub.
Dummies including BetterDummy is now intentionally skipped from controlling displays (
Display.isDummychecks).Virtual Displays (like Sidecar, Airplay, DisplayLink displays) that support only shade control are banned from control when in mirrored setups (
DisplayManager.isDisqualifiedFromShade).Each of these factors are prohibiting BetterDummy mirrored Virtual Displays to benefit from shade based dimming.
An exception must be implemented to solve this issue.
@Fariusz commented on GitHub (Feb 8, 2022):
Should it work at this point? I use displaylink and BetterDummy.
@waydabber commented on GitHub (Feb 9, 2022):
Hmm. Yes, BetterDummy->Sidecar/DisplayLink mirrored display brightness control via shading should be working in the latest version under Monterey.
@Fariusz commented on GitHub (Feb 10, 2022):
How about Big Sur? Should it work as well?
@waydabber commented on GitHub (Feb 10, 2022):
Probably should, but never tried it. :)
The No Control / unspecified control status is interesting though, I did program the app to show that message as a last resort - it seems like the app just has no idea what to do with a combination of DisplayLink and BetterDummy on Intel.
A few questions:
What might help is if you could provide me with the console log of the app during startup, when the display detection is done. Here is how to do that: https://github.com/MonitorControl/MonitorControl/discussions/851