Skip to content

v2.18.0

Choose a tag to compare

@ulsklyc ulsklyc released this 17 Aug 09:04
· 17 commits to main since this release

Added

  • Anything with a date can count down to it (#647). A calendar event and a task can each be marked "count down on the overview", and a Key dates tile then shows them together, sorted by how near they are - the holiday and the driving licence in one list, each row still leading back to its own module: tapping a task opens that task, tapping an event opens that day in the calendar. The wording is coarse while the date is far off and exact once it is near: "about 3 years", "about 9 months", then plain days from 30 out, because "10 days until the licence expires" has to stay 10 days. There is no threshold to configure - a question about a display detail is one nobody wants to be asked. The colour says how soon, not where the entry came from: what is due today or tomorrow is amber, what has passed is red, and the module the row belongs to keeps its colour on the mark at the left. This is one flag on each of two things that already exist rather than a third kind of entry: a holiday you already keep in the calendar does not have to be written down twice, and a licence that is not an appointment does not have to be pushed into the calendar to get a number. On a task the flag survives the reset, which is the point of the whole thing - a task that repeats from the day you tick it off ("always another N years", "N days after cleaning the filter") keeps counting down through every cycle. The switch needs a due date and stays locked without one, instead of saving something that would never appear. On an event the mark stays local: it is not sent to Google or CalDAV and it is not overwritten when a sync run comes back, the same way the icon and the visibility setting already behave. A date that has passed stays for another week ("3 days ago") rather than vanishing on the morning after - a licence expiry that disappears exactly when the consequence begins would leave you alone in the one moment you set it for; a recurring entry is never "expired" and keeps pointing at its next turn. What does not fit in the tile is counted at the bottom ("+2 more") instead of being cut off silently. The tile is not offered at all while nothing is marked, so a household that does not use this sees nothing new, and it appears at its saved position with the first countdown. It is deliberately not in the agenda view: the agenda answers what is happening in the coming days, and a countdown resolving in 2027 would sit at the bottom of every one of them.