[GH-ISSUE #1758] Screen to control: Depends on used keyboard #972

Closed
opened 2026-05-05 06:57:49 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @DennyWeinberg on GitHub (May 9, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1758

Before opening the issue, have you...?

  • Searched for existing issues

Hi, let's say I have built in monitor M1 and external monitor M2, with builtin keyboard K1 and external keyboard K2.
I don't want to move the cursor to the display I want to change.

Describe the solution you'd like

Independently to the mouse cursor, when K1 is used, M1 should change. When K2 is used, M2 should change.
A new option makes everything backward compatible.

Describe alternatives you've considered

Move the mouse cursor.

Anything else?

No response

Originally created by @DennyWeinberg on GitHub (May 9, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1758 ### Before opening the issue, have you...? - [x] Searched for existing issues ### Is your feature request related to a problem? Please describe Hi, let's say I have built in monitor M1 and external monitor M2, with builtin keyboard K1 and external keyboard K2. I don't want to move the cursor to the display I want to change. ### Describe the solution you'd like Independently to the mouse cursor, when K1 is used, M1 should change. When K2 is used, M2 should change. A new option makes everything backward compatible. ### Describe alternatives you've considered Move the mouse cursor. ### Anything else? _No response_
Author
Owner

@waydabber commented on GitHub (Jul 13, 2025):

Although the idea is valid, I don't think this will be added to MonitorControl as it's a rather specific request. An alternative solution might be to use BetterDisplay and use the app's CLI features to control the brightness of specific displays - you can use apps like Karabiner (that can manage keyboards separately) and bind scripts/commands to specific shortcuts of specific keyboards.

<!-- gh-comment-id:3067034470 --> @waydabber commented on GitHub (Jul 13, 2025): Although the idea is valid, I don't think this will be added to MonitorControl as it's a rather specific request. An alternative solution might be to use [BetterDisplay](https://betterdisplay.pro) and use the app's [CLI features](https://github.com/waydabber/BetterDisplay/wiki/Integration-features,-CLI) to control the brightness of specific displays - you can use apps like Karabiner (that can manage keyboards separately) and bind scripts/commands to specific shortcuts of specific keyboards.
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#972
No description provided.