![]() Therefore, I can imagine that it is best to only actually generate the Objects that are within x iterations of the recurrence setting (either a fixed number or something dynamic, for example, only the next 4 Objects when set to daily, only next 4 when set to Weekly, only next 12 when set to Monthly, only next 4 when set to Quarterly, only next 2 if set to Yearly). This will be an issue in Anytype as everyone might use their own way to mark a Task done, and for certain repeating/recurring Objects, it is irrelevant to mark the Object as “Done”. In the case of MS To Do, there is NO new Task created if the open Task is not marked as complete. This would ensure there is not an (endless) list of Tasks created immediately upon creating a first recurring Task (or in Anytype an Object of Type Task/Note/etc.), but only when relevant. When you mark the Task as done, a new Task is automatically created with a new Due Date based on the recurrence configured in the Repeat option. When creating a new Task in MS To Do you can set a Repeat option (Daily, Weekdays, weekly, Monthly, Yearly, or Custom). ![]() I think we can take a learning from how recurring/repeating tasks work in Microsoft To Do as outlined in the last section of this support article: Add due dates and reminders in Microsoft To Do - Microsoft Support
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |