Open full view…

Large date range and “days” calendar used

Mon, 27 Nov 2017 09:27:21 GMT

This is strictly speaking not an iPad beta problem/limitation as the Mac app has the same thing happening but its driving me crazy while I'm beta testing. I’m writing a futuristic dystopian novel where the Gregorian calendar no longer exists. The events of the novel happen over a 28 day period so I've set the timeline to “days”, however the pre-novel events which I need in my timeline occur over a 316 year period. This causes the Mac and iPad timeline to display some interesting dates for the start, end, and ages of characters. For example: the first event has a start date of “Day -115726” (I’ve set the date of the page 1 events to 0 set pre-novel events are negative). 1. Is it possible for the iOS app and Mac app to display years when the calendar is set to days but the numbers are large. 2. The iOS app displays some weird numbers in the event edit window (see attached). [66133C35-A3CB-41D3-91D9-22FE77EC5DBA](//

Matthew Tobin
Mon, 27 Nov 2017 10:05:28 GMT

Hi, I must admit, I had not envisaged the daily calendar being used with such a huge date range. The issue with converting long days to months or years is that those items are technically variable, and so without it being fixed at an absolute date, it isn't technically possible to make that calculation. This is also the reason we don't have a floating month calendar. I understand in your circumstances you probably don't care about it being exacting in that conversion, but I am concerned about the precedent where the calculations would change if you choose to then fix your timeline to an absolute date (we allow users to swap back and forth between the modes).

Mon, 27 Nov 2017 17:51:35 GMT

Thank you for your reply. I realise this is beyond the scope of the beta release and perhaps any future releases. However, I can think of many books that would be in the same situation including the book I'm reading now — The Hobbit. Also, almost all real-life ancient calendars use days and years (or at least seasons) as the basis of the calendar. Finally the calendar wouldn't change. There are exactly 365.2425 days in a year. But there could be rounding issues. Just food for thought.

Matthew Tobin
Mon, 27 Nov 2017 19:26:26 GMT

Yes, It is definitely an area where we would like to add more flexibility in the future, but it is out of scope for the current beta release. I understand your point that years are actual always the same length, but all of the maths in the date calculations necessitates the calculations being round numbers. The best we could to ably do is calculated the "-100 years" off the "zero date" stored in the calendar at the time... but that would mean the dates would visibly change if the zero date moved (e.g. -100 years might become -99 years 364 days" for instance. At least that is the case currently, because internally we store everything as time stamps and convert to the relative date txt only as a visual step. This allows us to convert easily from relative back to absolute, and keeps one set of date calculations within the app (so less can go wrong). Anyway, we can park the discussion for now, but it is on our list to review later.