mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #60] Fn key is not working even on ver 1.3.0 #56
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#56
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 @meow2 on GitHub (Jan 23, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/60
Hi, @the0neyouseek , thank you very much for developing this app! I'm a big fun of it.
Currently, I can't use (fn + F1) or (fn + F2) to adjust brightness (also to adjust sound with F10-12). As other users have reported, F1, F2, F10, F11, and F12 are overwritten as though I checked "Use F1, F2, etc. keys as standard function keys" in Keyboad, System Preferences.
I'm using MacBook Pro Mid 2014 with LG 24UD58, and also "⌘英かな.app", which is a key changer app enabling left and right command keys to work as Japanese substitution keys. But this seems to have nothing to do with MonitorControl, because the problems still remains after I quit ⌘英かな.app.
Would be very appreciated if you fixed this bug.
Thank you in advance.
@mlauria93 commented on GitHub (Mar 18, 2019):
Same bug here Function keys aren’t working at all nor the volume neither the brightness: I am using an LG 32UD99-W connected via Type-C to a MBP(2017)
@kn666 commented on GitHub (Apr 11, 2019):
https://github.com/JoniVR/MonitorControl/releases/tag/1.3.1 fork build includes fix and works for me
@reitermarkus commented on GitHub (May 7, 2019):
This should be fixed now.