-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
"Terminate Activity By Click" Setting Doesn't Properly Disable #283
Comments
Zakkumaru
changed the title
Terminate Activity By Click Doesn't Properly Disengage
"Terminate Activity By Click" Setting Doesn't Properly Disable
Nov 27, 2019
Thanks for the details to reproduce. There is an issue around here with the deselecting. I also experience it sometimes myself, when the reaction time (again) is too slow and I already start to activate the next activity (which I do from time to time, when I forgot before and record it later and adjusting the start time via the history.) and then end up in having the same activity active two times in parallel... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have noticed that when you turn off the setting to have activities terminate by clicking them again, it still allows you to terminate them and replace the activity field with the default,
<No Activity Selected>
.<No Activity Selected>
, which defies the settings in the app's menu. This also leads to the creation of sloppy entries in the log, with overlapping timestamps, causing strange things to happen with the "Adjacent Entry" algorithms, if you will.<No Activity Selected>
.The text was updated successfully, but these errors were encountered: