Skip to content
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

WIP: stop tracking when destroy signal is received #355

Closed
wants to merge 1 commit into from

Conversation

xai
Copy link

@xai xai commented Feb 1, 2023

When the destroy signal is received and the gnome extension is disabled, e.g., by locking the screen, it is safe to assume that the current activity can be stopped.

Fixes #354

How to test:

  1. Start tracking an activity
  2. Lock the gnome-session
  3. Unlock the gnome-session
  4. Verify that no activity is being tracked

When the destroy signal is received and the gnome extension is disabled,
e.g., by locking the screen, it is safe to assume that the current
activity can be stopped.

Signed-off-by: Olaf Lessenich <[email protected]>
@xai xai changed the title feat: stop tracking when destroy signal is received WIP: stop tracking when destroy signal is received Feb 1, 2023
@xai
Copy link
Author

xai commented Feb 1, 2023

Needs to be revised, as noted in #354 (comment).

@mwilck
Copy link
Contributor

mwilck commented Sep 25, 2023

As noted above, this feature doesn't belong in the extension. It should be implemented in hamster itself.

@mwilck mwilck closed this Sep 25, 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.

Stop tracking when destroy signal is received (e.g., due to screen lock)
2 participants