-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Tool tips for due/threshold dates and recurrences #511
Comments
This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now. |
I think this is still relevant. |
@warmwaffles @dlaidig although not the exact solution for this request, you might want to check out the latest pre-release, it contains part of it, the conversion of dates to human friendly ones. It can be enabled in settings. We should be able to use the function to work out the tool tips here. |
I've tested this a while ago with sleek-2.0.12-rc.3 and thought that I commented here but that apparently got lost. My first reaction was "wow, this feature solves 99% of my personal use case" (while tool tips with more information are still a good idea). I was quite happy to see "t: 4 days ago" instead of a date. And opening the dialog to edit the task still allowed me to see the actual date. Now I updated to sleek-2.0.12 and it shows me "t: elapsed" instead of "t: 4 days ago". This is really not useful since non-elapsed tasks are hidden anyway. When changing the filter to show tasks with threshold dates in the future, I also noticed that for tasks with "t:2024-04-01" it shows "t: next month". I guess this is technically true, but it gives my brain the impression that I still have a few weeks before this gets relevant. I would rather prefer to see "t: in 5 days". |
You indicated in #224 that the tool tips should be tracked in a separate issue, so here it is.
My original comment was:
@warmwaffles added
In more detail:
+
.)(I'm aware this is not the most specific description. I was just trying to collect some ideas to potentially extend my original idea. Take what you find useful and ignore the rest.)
The text was updated successfully, but these errors were encountered: