-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use screen saver/locker to tag inactivity #39
Comments
Hi! That sounds like a nice and reasonable extension! |
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Dec 6, 2020
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Dec 6, 2020
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
3 tasks
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Feb 21, 2021
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Mar 5, 2021
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Mar 5, 2021
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Mar 5, 2021
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Mar 9, 2022
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
liskin
added a commit
to liskin/arbtt
that referenced
this issue
Mar 10, 2022
Tracking inactivity via idle time is unsuitable if one wants to account for activities such as watching movies or reading difficult texts. As media players usually keep the screen saver/locker from triggering, tracking inactivity that way might be more accurate, as long as the screen saver trigger is set to low enough duration or the user diligently locks their screen when walking away. Currently implemented for X11 only, and even that implementation supports only a few desktop environments. Relates: nomeata#39
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd love to be able to track activities such as watching a movie or reading a dense (no scrolling for long time) blogpost, so tagging inactivity by idle time isn't suitable for my use cases. I happen to be quite consistent in locking the screen whenever I walk away, and should I forget, xss-lock takes care of it, so I'd like to use that for inactivity tagging. Unfortunately, the screen saver is transparent to xmonad/ewmh, so it's not being captured.
I guess I'd need to extend the capture format with this and then capture https://hackage.haskell.org/package/X11-1.9/docs/Graphics-X11-XScreenSaver.html#t:XScreenSaverState in addition to the idle time. Is this something possibly useful for others, shall I submit a PR then?
The text was updated successfully, but these errors were encountered: