[GH-ISSUE #855] Link internal keyboard to internal display, external keyboard to external display #539

New issue

Closed

opened 2026-05-05 06:12:16 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:12:16 -06:00

Owner

Originally created by @lukeshingles on GitHub (Dec 22, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/855

Before opening the issue, have you...?

Searched for existing issues

I use MonitorControl to replace the brightness-key functionality that I had with a Thunderbolt Display, but now with a non-Apple display connected to my MacBook Pro. It works great! But there is an inconsistency. When using the Thunderbolt Display, the MBP brightness keys only control the MBP display, and the external Bluetooth keyboard controls the Thunderbolt display (or other external displays).

Describe the solution you'd like

I would like the behaviour to match what happens when an Apple external display is connected to a MacBook Pro.

In the preferences, under the Keyboard -> Screen to Control, add an option to differentiate between the MBP keyboard brightness keys (for MBP display) and external keyboard brightness keys (for external monitors). It could be called something like 'Depends on internal/external keyboard'.

Describe alternatives you've considered

The internal/external keyboard distinction could be a checkbox below the existing 'Screen to Control' options, since if I recall correctly when I had both a Thunderbolt Display and an Apple Cinema Display connected, the external keyboard would then control whichever display had the cursor (but not the internal display).

Anything else?

No response

Originally created by @lukeshingles on GitHub (Dec 22, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/855 ### Before opening the issue, have you...? - [X] Searched for existing issues ### Is your feature request related to a problem? Please describe I use MonitorControl to replace the brightness-key functionality that I had with a Thunderbolt Display, but now with a non-Apple display connected to my MacBook Pro. It works great! But there is an inconsistency. When using the Thunderbolt Display, the MBP brightness keys only control the MBP display, and the external Bluetooth keyboard controls the Thunderbolt display (or other external displays). ### Describe the solution you'd like I would like the behaviour to match what happens when an Apple external display is connected to a MacBook Pro. In the preferences, under the Keyboard -> Screen to Control, add an option to differentiate between the MBP keyboard brightness keys (for MBP display) and external keyboard brightness keys (for external monitors). It could be called something like 'Depends on internal/external keyboard'. ### Describe alternatives you've considered The internal/external keyboard distinction could be a checkbox below the existing 'Screen to Control' options, since if I recall correctly when I had both a Thunderbolt Display and an Apple Cinema Display connected, the external keyboard would then control whichever display had the cursor (but not the internal display). ### Anything else? _No response_

gitea-mirror

2026-05-05 06:12:16 -06:00

closed this issue
added the
Status: Abandoned

enhancement
labels

gitea-mirror commented

2026-05-05 06:12:22 -06:00

Author

Owner

@waydabber commented on GitHub (Dec 22, 2021):

Theoretically it is possible to differentiate between the internal and external media keys, but the library used by MC (MediaKeyTap) does not distinguish between them. Currently MC controls the screen that has the mouse.

@waydabber commented on GitHub (Dec 22, 2021): Theoretically it is possible to differentiate between the internal and external media keys, but the library used by MC (MediaKeyTap) does not distinguish between them. Currently MC controls the screen that has the mouse.

gitea-mirror commented

2026-05-05 06:12:25 -06:00

Author

Owner

@stale[bot] commented on GitHub (Dec 22, 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.

@stale[bot] commented on GitHub (Dec 22, 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.