Monitorcontrol: Fix F14/F15 keys for native Apple Keyboards (They should not change brightness)

Created on 2 Jun 2019  Â·  6Comments  Â·  Source: MonitorControl/MonitorControl

I have an issue with F14/F15 keys. When this app is launched, F15 decreases brightness and F15 increases brightness, but that is not an action I want them to do.
If I kill MonitorControl, this issue disappears.

By default, macOS uses those keys for non-Apple devices to control display brightness, but I've disabled that already. The issue is with this app itself or one of its dependencies.

It seems like this app deliberately listens for F14/F15 keypress to change brightness.

I want to be able to disable this behavior as a user.

I know that these keys are used by hackintoshes when rerouting brightness keys (exactly to F14/F15) to work in macOS, and thus assume that this is a feature for them.
But it bothers me a lot, cause I use F14/F15 for custom actions.

Please, add an option to disable this behavior. It would be great.

Minor Bug

Most helpful comment

I experience the small annoying behaviour with F14/F15 as well as the eject key. Unfortunately this is a dealbreaker since I have those mapped to another application. +1 for high priority.

All 6 comments

I experience the small annoying behaviour with F14/F15 as well as the eject key. Unfortunately this is a dealbreaker since I have those mapped to another application. +1 for high priority.

Same here. This is currently the only downside of this wonderful tool as F14/F15 is used by me for other global shortcuts already which don't work anymore if I start MonitorControl.

Agree, it seems the un-modified key codes (at least on this Magic Keyboard with Numpad), for F14 and F15 are :

Key Down
    Characters: 
    Unicode:        63249 / 0xf711
    Keys:       F14
    Key Code:   107 / 0x6b
    Modifiers:  8388864 / 0x800100 ⓘ

Key Down
    Characters: 
    Unicode:        63250 / 0xf712
    Keys:       F15
    Key Code:   113 / 0x71
    Modifiers:  8388864 / 0x800100 ⓘ

And this projects dependancy on MediaKeyTap means that both these key codes are intercepted for Brightness events in functionKeyCodeToMediaKey() :
https://github.com/the0neyouseek/MediaKeyTap/blob/a1bb7490ee66438f6c83c2c26aa35608c7d1ef0c/MediaKeyTap/MediaKeyTap.swift#L129

I'm using the recently released version 2.1.0, and the F14/F15 keys are still being intercepted by MonitorControl.

That's correct, this isn't implemented in MonitorControl yet, I provided a parameter in MediaKeyTap to ignore those keys but the default is still to listen for them, so we don't break existing behaviour.

I was planning on adding this as an option in preferences. Feel free to open a PR to do it yourself if you don't want to wait for me to do it soon, sorry if you were hoping 2.1.0 would already fix it.

My bad, I saw the merged PR above and thought the fix was in!

Was this page helpful?
0 / 5 - 0 ratings