Closed vincentbernat closed 1 year ago
Is it too late to rename the option? Depending on XSECURELOCK_BLANK_DPMS_STATE
, the option may be misnamed. I think it should be XSECURELOCK_SAVER_STOP_WHEN_BLANKED
(or ON_BLANK
).
As this is a rather unusual feature, I guess it's OK to rename.
Am Di., 18. Okt. 2022 um 13:31 Uhr schrieb Vincent Bernat < @.***>:
Is it too late to rename the option? Depending on XSECURELOCK_BLANK_DPMS_STATE, the option may be misnamed. I think it should be XSECURELOCK_SAVER_STOP_WHEN_BLANKED (or ON_BLANK).
— Reply to this email directly, view it on GitHub https://github.com/google/xsecurelock/pull/154#issuecomment-1282968443, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB5NMEO3RQV5ODSHD4NF3DWD4CKDANCNFSM6AAAAAARDVTFDE . You are receiving this because you modified the open/close state.Message ID: @.***>
This is a patch embedded in #139, but as this is unlikely to be merged, I am submitting it separately. The use case is that if the screensaver takes some time to start but does not eat CPU, this may be interesting to leave it running (in my case, it starts fast, but it takes some time to display all the information on it).