mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #30] Hotkeys doesn't work on fullscreen app on second display #28
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#28
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 @nekrasovdmitriy on GitHub (Apr 14, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/30
Originally assigned to: @the0neyouseek, @waydabber on GitHub.
If any app is open in fullscreen on second monitor, hot keys of MonitorControl on that monitor doesn't work, you have to switch back to desktop view on second display to have them work again.
On main display hot keys work anywhere, on fullscreen apps also.
@the0neyouseek commented on GitHub (Apr 14, 2018):
Hi @nekrasovdmitriy,
That's weird, the hot keys should work independently of the monitor used and not be affected by fullscreen apps at all.
What could be the problem here is that the app determine what screen to apply the hot key to directly from the system using NSScreen main. This function choose the 'current' screen depending on keyboard, mouse focus and usage.
So, for example, if you've just launched an app in fullscreen and moved your mouse with no further interaction with the app nor the second screen yet, the hot key would be applied to the previous screen.
There's nothing I can really do about this behaviour as it's native.
Is this what's happening to you ?
@ifixr commented on GitHub (Jun 18, 2018):
I can confirm this. I'm reading this thread in Safari in full screen and hitting the brightness keys control my built-in screen.
@the0neyouseek commented on GitHub (Jun 21, 2018):
Hi @ifixr & @nekrasovdmitriy,
As i'm currently working full time, I don't have much free time to develop MonitorControl but I'll try to look this up asap and fix it in the next version.
Have a nice day.
@odenak commented on GitHub (Aug 14, 2019):
I also have this problem, but I found that occasionally after my MBP wakes from sleep, it does work on the fullscreen apps on the external monitor.
@kikiwora commented on GitHub (Oct 24, 2019):
The same issue here.
But for me, the second monitor is actually the primary monitor of two of them due to issues with brightness control via HDMI on Mac Mini 2018.
As for me, this is at least medium priority, since it greatly impacts user flow
+1 for higher priority
If I enable the first monitor (connected to HDMI, where brightness control does not work) in MonitorControll, brightness of the second display is control from both first and second display, but if users are on the app that is full screen on a second display, brightness is controlled, but OSD is displayed on the first screen.
The same issue occurs on a first monitor - it controls the second display but displays OSD on the first one.
And yeah, OSD for first and second displays are logically divided (means they save separate brightness levels, just as they should do for 2 monitors), but for some reason both control only the second display. And if I disable the first display (that is connected via HDMI), then I cannot control the brightness of the second display in full-screen apps at all.
The temporary solution - either stay with both displays enabled in MonitorControl, even if one of them is not changing it's brightness or enable brightness synchronisation between all displays
@quantumgolem commented on GitHub (Jun 6, 2020):
Thank you for the reference
@quantumgolem commented on GitHub (Oct 7, 2020):
@JoniVR Hey, was this issue ever fixed? I just downloaded version 2.1.0 but it seems like brightness controls still don't work in full screen apps (and they never did for me). Maybe there was a regression?
@JoniVR commented on GitHub (Oct 7, 2020):
Hmm it should be, I'll take a another look when I get time.
@nekrasovdmitriy commented on GitHub (Oct 7, 2020):
I can confirm that problem still persists
@quantumgolem commented on GitHub (Oct 19, 2020):
@JoniVR Thanks a lot! I think I've updated to every version since the issue was opened, but the issue was never fixed on any of the versions as far as I can tell. Looking forward to it, since this is one of my most used apps :D
@shahanesanket commented on GitHub (Nov 2, 2020):
Hi @JoniVR , this problem still exists. Hack to get it working is to leave the monitor control window open on the desktop of the second screen, then the hotkeys then work on full screen apps as well. It would be very useful to have it working without this hack. Thanks!
@nekrasovdmitriy commented on GitHub (Nov 2, 2020):
Hack works
@quantumgolem commented on GitHub (Dec 19, 2020):
I just found out about Lunar. It seems to work fine in fullscreen apps and also has some more advanced features I'm interested in. I'll miss MonitorControl! It's a great app.
@waydabber commented on GitHub (Aug 20, 2021):
Hi, this should be fixed in an upcoming 3.0.0 version (beta8 still do not have this). The location of the mouse cursor will determine the controlled display including if the given screen has a full screen app (previous implementation failed on this).
https://github.com/MonitorControl/MonitorControl/issues/424
@waydabber commented on GitHub (Aug 20, 2021):
If you have any issue with this in the upcoming 3.0.0 version, please let me know here.
https://github.com/MonitorControl/MonitorControl/issues/424
I'll close this issue since more technical details are available over there.
Thank you!