newmarcel / newmarcel/KeepingYouAwake
allow display to sleep vs locking
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 6.9k
- Forks
- 266
- PR merge metrics
- No merged PRs in 30d
Description
I was trying the option "Allow the display to sleep" but it didn't really behave the way I thought it would.
The display did indeed went into sleep. But then after re-activation it asked for a password.
That's not what I would have expected from the wording.
I was thinking I would not have to login as it would just sleep/dim the screen.
So I assume it means the machine keeps running (not sleeping) with the screen dimmed - but it also gets locked?
I think it would be good to make this a bit clearer from the option text.
But thanks for the app - I use it all the time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the “Allow the display to sleep” option text in the app and review how its locking and password behavior is described. Done means the wording clearly sets expectations about display sleep, continued machine activity, and whether reactivation requires login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, objective-c
- Domain
- desktop, operating-systems
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100