[GH-ISSUE #3] Fix keyboard shortcut #3

New issue

Closed

opened 2026-05-05 04:40:31 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 04:40:31 -06:00

Owner

Originally created by @the0neyouseek on GitHub (Jan 1, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/3

Originally assigned to: @the0neyouseek on GitHub.

In this issue I will focus on working on my own system to handle the brightness and volume key. I will also allow the key to be pass-through, meaning that if your current screen is a native display, the app will simply pass the command to macOS default, changing the brightness/volume natively.

Hopefully this will fix the following issues :

Karabiner Elements dependency
Using the shortcut keys while in an app making use of the same shortcuts would result in the app registering the shortcut too.
You could not change a native display brightness/volume using Karabiner Elements as it would override the default key.

I'll update the issue when the dev of the features discussed will be completed.

Originally created by @the0neyouseek on GitHub (Jan 1, 2018). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/3 Originally assigned to: @the0neyouseek on GitHub. In this issue I will focus on working on my own system to handle the brightness and volume key. I will also allow the key to be *pass-through*, meaning that if your current screen is a native display, the app will simply pass the command to macOS default, changing the brightness/volume natively. Hopefully this will fix the following issues : - `Karabiner Elements` dependency - Using the shortcut keys while in an app making use of the same shortcuts would result in the app registering the shortcut too. - You could not change a native display brightness/volume using `Karabiner Elements` as it would override the default key. --- *I'll update the issue when the dev of the features discussed will be completed.*