Skip to content

Conversation

@vincentbernat
Copy link
Contributor

The correct name should be XSECURELOCK_SAVER_STOP_ON_BLANK. We also starts children when screensaver is on, but screen is not blanked, or when screensaver is one and screen is blanked, but this option is not enabled.

I can do a separate pull request for this one-line change if you prefer. Then, I get the same behaviour than #139 by setting XSECURELOCK_BLANK_TIMEOUT=-1.

The correct name should be XSECURELOCK_SAVER_STOP_ON_BLANK. We also
starts children when screensaver is on, but screen is not blanked, or
when screensaver is one and screen is blanked, but this option is not
enabled.
@anthraxx
Copy link

@divVerent any updates, do you want to pull this in? I'm asking as I'd also like to request if a new release can be issued which contains this feature? It has been a rather long time now.

@divVerent
Copy link
Contributor

Oh sorry, I missed this. Yes, this change is uncontroversial, getting it in.

@divVerent divVerent merged commit 8a448bd into google:master Jul 21, 2023
@divVerent
Copy link
Contributor

Thank you!

tzeikob added a commit to tzeikob/xsecurelock that referenced this pull request Aug 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants