mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1758] Screen to control: Depends on used keyboard #972
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#972
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 @DennyWeinberg on GitHub (May 9, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1758
Before opening the issue, have you...?
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
@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.