github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #1723] Custom keyboard shortcuts continue capturing events when not in `Custom keyboard shortcuts` mode #953

New issue

Open

opened 2026-05-05 06:55:50 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:55:50 -06:00

Owner

Originally created by @tyirvine on GitHub (Jan 22, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1723

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

When Brightness and contrast: is set to Custom keyboard shortcuts the application allows you to set two shortcuts.

If these shortcuts are set they continue to capture keyboard events even when Brightness and contrast: is set to a different option.

Once the shortcuts are removed keyboard events behave normally.

Steps to reproduce

Open settings
Go to the Keyboard section
Select Custom keyboard shortcuts from Brightness and contrast:
Record shortcuts
Switch Brightness and contrast: to some other option
Attempt to use the shortcuts in some other application

Expected behavior

It is expected that the shortcuts would work normally in some other application.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 15.0.1 (24A348)
- Mac model: –
- MonitorControl version: 4.3.3
- Monitor(s): –
- Apple Silicon/M1 (yes or no): –

Originally created by @tyirvine on GitHub (Jan 22, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1723 ### Before opening the issue, have you...? - [x] Searched for existing issues - [x] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [x] Updated MonitorControl to the latest version (if applicable) ### Describe the bug When `Brightness and contrast:` is set to `Custom keyboard shortcuts` the application allows you to set two shortcuts. If these shortcuts are set they continue to capture keyboard events even when `Brightness and contrast:` is set to a different option. Once the shortcuts are removed keyboard events behave normally. ### Steps to reproduce 1. Open settings 2. Go to the `Keyboard` section 3. Select `Custom keyboard shortcuts` from `Brightness and contrast:` 4. Record shortcuts 5. Switch `Brightness and contrast:` to some other option 6. Attempt to use the shortcuts in some other application ### Expected behavior It is expected that the shortcuts would work normally in some other application. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 15.0.1 (24A348) - Mac model: – - MonitorControl version: 4.3.3 - Monitor(s): – - Apple Silicon/M1 (yes or no): – ```

gitea-mirror added the

bug

label 2026-05-05 06:55:50 -06:00

gitea-mirror commented

2026-05-05 06:55:53 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 24, 2025):

Yes, it's an issue maybe (or one can think of it as a design choice, not sure how should I classify it) - obviously the simple workaround is just remove these shortcuts.

@waydabber commented on GitHub (Jan 24, 2025): Yes, it's an issue maybe (or one can think of it as a design choice, not sure how should I classify it) - obviously the simple workaround is just remove these shortcuts.

gitea-mirror commented

2026-05-05 06:55:55 -06:00

Author

Owner

@lucasilverentand commented on GitHub (Apr 13, 2025):

Could this be related to the when I do not have monitor control running and then my brightness keys stop working

@lucasilverentand commented on GitHub (Apr 13, 2025): Could this be related to the when I do not have monitor control running and then my brightness keys stop working

gitea-mirror commented

2026-05-05 06:55:57 -06:00

Author

Owner

@pitkant commented on GitHub (May 9, 2025):

I also have this issue. I have a Magic Keyboard with numpad that has extra function keys F13-F19 and for some reason F14 and F15 are pre-assigned to decrease and increase monitor brightness. I have unchecked them in the Keyboard Shortcuts - Display menu but they still continue to function as brightness controls when MonitorControl (4.3.3) is on.

I am happy that F1 and F2 work as brightness controls with Monitor Control but I would like to assign F14 and F15 to other functions.

@pitkant commented on GitHub (May 9, 2025): I also have this issue. I have a Magic Keyboard with numpad that has extra function keys F13-F19 and for some reason F14 and F15 are pre-assigned to decrease and increase monitor brightness. I have unchecked them in the Keyboard Shortcuts - Display menu but they still continue to function as brightness controls when MonitorControl (4.3.3) is on. I am happy that F1 and F2 work as brightness controls with Monitor Control but I would like to assign F14 and F15 to other functions.

gitea-mirror commented

2026-05-05 06:55:59 -06:00

Author

Owner

@niklasravnsborg commented on GitHub (Mar 12, 2026):

I also have the same problem, I'm normally able to trigger the normal F1 or F2 functionality of an app, when hitting fn + F1. But as soon as MonitorControl is open, this doesn't work anymore - even with the setting Disable Keyboard...

@niklasravnsborg commented on GitHub (Mar 12, 2026): I also have the same problem, I'm normally able to trigger the normal F1 or F2 functionality of an app, when hitting `fn` + `F1`. But as soon as MonitorControl is open, this doesn't work anymore - even with the setting `Disable Keyboard`...