mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #563] Keyboard shortcut to change external display only #423
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#423
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 @avichou on GitHub (Sep 5, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/563
Originally assigned to: @waydabber on GitHub.
Before opening the issue, have you...?
Is your feature request related to a problem? Please describe
impossibilty to change external display brightness only
Describe the solution you'd like
im extremely thankful of being able to use ddc on m1 now !
just wanted to submit an idea which i am suprised not to see implemented yet:
using a custom shortcut ,whatever it be ,to control external display brightness only ,while keeping macbook display at the same brightness (in my case 0 nits/off )
Describe alternatives you've considered
im extremely thankful of being able to use ddc on m1 now !
just wanted to submit an idea which i am suprised not to see implemented yet:
using a custom shortcut ,whatever it be ,to control external display brightness only ,while keeping macbook display at the same brightness (in my case 0 nits/off )
Anything else?
No response
@waydabber commented on GitHub (Sep 6, 2021):
There is a shortcut to change brightness for the internal display only (ctrl+brightness), we could add an other that does this in reverse and change external displays only (shift+ctrl+brightness).
@avichou commented on GitHub (Sep 6, 2021):
thanks that would be awesome !! also yes my syntax sucks ahaha
@waydabber commented on GitHub (Sep 9, 2021):
I added this to 3.1.0. There is an unsigned interim version here to test.
Update: the shortcut is now changed to ctrl+command+brightness (shift+ctrl+brightness was colliding with fine control if somebody wants to control internal display only)
@avichou commented on GitHub (Sep 9, 2021):
works wonders,amazing ! i assume it'll be released as stable or at least beta ,within the next couple of days right?
thanks again and have a good day!
@waydabber commented on GitHub (Sep 9, 2021):
We don't have an exact timetable, but surely we'll release it eventually. :)
@Converseallstar95 commented on GitHub (Sep 20, 2021):
Thanks for this suggestion I was just looking for it as a new MonitorControl user!
I just switched away from my two Thunderbolt Displays and they worked as follows, if I pressed the volume or brightness keys on my wireless keyboard, they only changed the external monitor. If I pressed those keys on the laptop, the only changed the laptop values.
Any way this can be added as an option for MonitorControl; thanks in advance!
@waydabber commented on GitHub (Sep 20, 2021):
Hi, this does not seem to be easily possible. MonitorControl uses MediaTapKey which does not currently distinguish between the brightness key from a Magic Keyboard and a built-in keyboard. MediaTapKey relies on IOKit's special key designations which also don't seem to distinguish between these. There is a distinction in real life of course and apparently some apps can capture this (for example Hammerspoon returns a different code for them and also Karabiner can distinguish between strokes from different keyboards). You might want to try to add a new Feature Request regarding differentiating between built-in/external keyboard keytaps here: https://github.com/MonitorControl/MediaKeyTap. If the devs make it work, MonitorControl can also implement something like this.
@Converseallstar95 commented on GitHub (Sep 21, 2021):
Thanks for the insight, I will try my luck with them. :)