[GH-ISSUE #211] MonitorControl consumes combo keypresses (⌘ + F15) instead of only F15/F14 #162

New issue

Closed

opened 2026-05-05 05:18:28 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:18:28 -06:00

Owner

Originally created by @varenc on GitHub (May 4, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/211

Originally assigned to: @waydabber on GitHub.

I have an obscure global keyboard shortcut setup on ⌘+F15. MonitorControl consumes any presses for media keys like F15, even when they're used with modifiers keys that have on effect on MonitorControl.

MonitorControl should only react when media keys are pressed by themselves, or when pressed with modifiers MonitorControl recognizes. So F15, Ctrl+Shift+F15 (small increment) and Ctrl+F15 (internal display), should all continue to work, but ⌘+F15, Ctrl+⌥+F15, etc, should not work and should not be consumed/blocked by MonitorControl.

Not sure if MediaKeyTap already supports aborting a key press consumption or not? But if it does, then fixing this might be as simple as observing unrecognized modifier key combinations in the delegate method here, and aborting.

Originally created by @varenc on GitHub (May 4, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/211 Originally assigned to: @waydabber on GitHub. I have an obscure global keyboard shortcut setup on ⌘+F15. MonitorControl consumes any presses for media keys like F15, even when they're used with modifiers keys that have on effect on MonitorControl. MonitorControl should only react when media keys are pressed by themselves, or when pressed with modifiers MonitorControl recognizes. So F15, Ctrl+Shift+F15 (small increment) and Ctrl+F15 (internal display), should all continue to work, but ⌘+F15, Ctrl+⌥+F15, etc, should not work and should not be consumed/blocked by MonitorControl. Not sure if MediaKeyTap already supports aborting a key press consumption or not? But if it does, then fixing this might be as simple as observing unrecognized modifier key combinations in the [delegate method here](https://github.com/the0neyouseek/MonitorControl/blob/5ed77ab05f7d794719043a7384c295fd8ef0204b/MonitorControl/AppDelegate.swift#L200), and aborting.

gitea-mirror

2026-05-05 05:18:28 -06:00

closed this issue
added the
bug

duplicate
labels

gitea-mirror commented

2026-05-05 05:18:33 -06:00

Author

Owner

@JoniVR commented on GitHub (Jun 10, 2020):

@JoniVR commented on GitHub (Jun 10, 2020): Related to this answer: https://github.com/MonitorControl/MonitorControl/issues/227#issuecomment-642090362

gitea-mirror commented

2026-05-05 05:18:37 -06:00

Author

Owner

@fancymans commented on GitHub (Jul 30, 2020):

Glad I was able to find out the culprit for killing my ⌘ + F15 custom app shortcut haha. Was wondering what it was that caused this issue. Agree it's relatively minor but would be very nice if it didn't block modifiers. Will have to map my shortcut to something else in the meantime.

@fancymans commented on GitHub (Jul 30, 2020): Glad I was able to find out the culprit for killing my ⌘ + F15 custom app shortcut haha. Was wondering what it was that caused this issue. Agree it's relatively minor but would be very nice if it didn't block modifiers. Will have to map my shortcut to something else in the meantime.

gitea-mirror commented

2026-05-05 05:18:40 -06:00

Author

Owner

@fono commented on GitHub (Apr 6, 2021):

+1 for this. For me brightness control works perfectly with the dedicated brightness keys on the external keyboard (F1, F2), and even touchbar brightness controls are working great. Thus, I don't need F14 and F15 to control brightness, but I was using them for other purposes which I would still need. It would be nice to have an option to disable these 'secondary' hotkeys, if it's not feasible to make it fully customizable. Regardless, this is an excellent app, thank you.

@fono commented on GitHub (Apr 6, 2021): +1 for this. For me brightness control works perfectly with the dedicated brightness keys on the external keyboard (F1, F2), and even touchbar brightness controls are working great. Thus, I don't need F14 and F15 to control brightness, but I was using them for other purposes which I would still need. It would be nice to have an option to disable these 'secondary' hotkeys, if it's not feasible to make it fully customizable. Regardless, this is an excellent app, thank you.

gitea-mirror commented

2026-05-05 05:18:42 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 20, 2021):

I think there should be an option to customize keyboard shortcuts. I am trying to focus and consolidate all issues like this into #118. I'll close this one as a duplicate now. Thank you!

@waydabber commented on GitHub (Aug 20, 2021): I think there should be an option to customize keyboard shortcuts. I am trying to focus and consolidate all issues like this into #118. I'll close this one as a duplicate now. Thank you!