mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #718] Save/restore brightness value in software mode #470
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#470
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 @xand3r40r93 on GitHub (Oct 16, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/718
Originally assigned to: @waydabber on GitHub.
Before opening the issue, have you...?
Is your feature request related to a problem? Please describe
I using my monitor on full brightness and controlling brightness in software mode. For my monitor, it's like 'flicker free' mode. After system restart brightness value always is 100%.
Describe the solution you'd like
Just save/restore brightness value in software mode at startup or closing program.
Describe alternatives you've considered
...
Anything else?
No response
@waydabber commented on GitHub (Oct 16, 2021):
The app actually saves software brightness but to avoid behavior that might be puzzling to some users, the saved software dimming values are restored only upon wake or display configuration change and not during application startup (it is intentional, most people probably don't restart their macs or the app very often anyway but use sleep instead). The
Upon startup or wake/Apply last saved valuesare relevant only for the DDC component of the brightness, not the software component (when waking from sleep, software dimming is reapplied regardless of this setting but on startup it is never reapplied). It might be reasonable to change how this works (we should clarify that theUpon startup or wakeoption is only for DDC only and there could be a setting about reapplying software dimming upon app startup).@waydabber commented on GitHub (Oct 17, 2021):
I did some tweaks here and there + changed the behavior. Now if
Upon startup or wake/Apply last saved valuesis selected, then software and combined brightness will be restored upon app start. Since this is not a default startup option and also there is a separate option for allowing zero brightness with a proper warning, this seems to be acceptable.@waydabber commented on GitHub (Oct 17, 2021):