[GH-ISSUE #456] Disable app when not connect to external monitor #362

Closed
opened 2026-05-05 05:50:02 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @LandonSchropp on GitHub (Jun 22, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/456

Originally assigned to: @waydabber on GitHub.

Checklist

  • I have searched for existing issues

Is your feature request related to a problem? Please describe.

Yes. When no monitors are connected, MonitorControl causes issues with the built-in brightness controls. This problem is described in more detail in #366.

Describe the solution you'd like

A simple solution would be to disable the app when no monitors are connected. This would allow the default system brightness controls to operate, and the app could re-enable itself when I connect to my external monitor. This could potentially be added as an option in the Preferences, but it might also make sense as a default behavior.

Describe alternatives you've considered

Right now I quit the app every time I unplug from my monitor and I restart it when I plug back in. This workflow isn't great.

Additional context

Nope.

Originally created by @LandonSchropp on GitHub (Jun 22, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/456 Originally assigned to: @waydabber on GitHub. **Checklist** <!-- Before you submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) --> - [x] I have searched for existing issues **Is your feature request related to a problem? Please describe.** Yes. When no monitors are connected, MonitorControl causes issues with the built-in brightness controls. This problem is described in more detail in #366. **Describe the solution you'd like** A simple solution would be to disable the app when no monitors are connected. This would allow the default system brightness controls to operate, and the app could re-enable itself when I connect to my external monitor. This could potentially be added as an option in the Preferences, but it might also make sense as a default behavior. **Describe alternatives you've considered** Right now I quit the app every time I unplug from my monitor and I restart it when I plug back in. This workflow isn't great. **Additional context** Nope.
gitea-mirror 2026-05-05 05:50:02 -06:00
Author
Owner

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

Hi, I made a change in the upcoming version - if there are no external displays connected, the app will disengage from listening to brightness/volume keys, handing back control to the OS. Hope this is what you requested!

<!-- gh-comment-id:901660974 --> @waydabber commented on GitHub (Aug 19, 2021): Hi, I made a change in the upcoming version - if there are no external displays connected, the app will disengage from listening to brightness/volume keys, handing back control to the OS. Hope this is what you requested!
Author
Owner

@mmontag commented on GitHub (Aug 19, 2021):

Nice!! Much appreciated

<!-- gh-comment-id:901775482 --> @mmontag commented on GitHub (Aug 19, 2021): Nice!! Much appreciated
Author
Owner

@LandonSchropp commented on GitHub (Aug 19, 2021):

Awesome! That's exactly what I wanted. Thank you!

<!-- gh-comment-id:902234671 --> @LandonSchropp commented on GitHub (Aug 19, 2021): Awesome! That's exactly what I wanted. Thank you!
Author
Owner

@LandonSchropp commented on GitHub (Aug 19, 2021):

@waydabber Just to clarify, does this also include the automatic brightness adjustments? One of the big issues I run into with MonitorControl on my MacBook is it aggressively makes the screen too bright when I'm not connected to an external monitor.

<!-- gh-comment-id:902236374 --> @LandonSchropp commented on GitHub (Aug 19, 2021): @waydabber Just to clarify, does this also include the automatic brightness adjustments? One of the big issues I run into with MonitorControl on my MacBook is it aggressively makes the screen too bright when I'm not connected to an external monitor.
Author
Owner

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

I think MonitorControl should not interfere with automatic brightness adjustments in any way as there is nothing implemented in the code that would do such a thing.

<!-- gh-comment-id:902684550 --> @waydabber commented on GitHub (Aug 20, 2021): I think MonitorControl should not interfere with automatic brightness adjustments in any way as there is nothing implemented in the code that would do such a thing.
Author
Owner

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

Hi, we have relased the 3.0.0 version. Could you please test if this issue is resolved and report back? Thank you!

<!-- gh-comment-id:903128603 --> @waydabber commented on GitHub (Aug 21, 2021): Hi, we have relased the [3.0.0 version](https://github.com/MonitorControl/MonitorControl/releases/tag/v3.0.0-rc1). Could you please test if this issue is resolved and report back? Thank you!
Author
Owner

@LandonSchropp commented on GitHub (Aug 21, 2021):

Sure thing! I've downloaded the update and I'll report back soon.

<!-- gh-comment-id:903158909 --> @LandonSchropp commented on GitHub (Aug 21, 2021): Sure thing! I've downloaded the update and I'll report back soon.
Author
Owner

@LandonSchropp commented on GitHub (Aug 21, 2021):

This update works perfectly. Thank you!

<!-- gh-comment-id:903163232 --> @LandonSchropp commented on GitHub (Aug 21, 2021): This update works perfectly. Thank you!
Author
Owner

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

Amazing, thanks for the feedback!

<!-- gh-comment-id:903172012 --> @waydabber commented on GitHub (Aug 21, 2021): Amazing, thanks for the feedback!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#362
No description provided.