I second this! I have come to rely on this lovely feature-- it can be very helpful to have ages in years, months, days. I can't fathom a reason for changing this.
For me, the advantage is the other way round. My project is history, not creative writing, and the age of the protagonists down to the day is irrelevant (& therefore just clutter). In may cases, the date of birth of the people involved is unknown & even when it is, I have entered just the birth year for all but the most important. Under v.2.2 Aeon would therefore state an age for participants in events that was both unnecessarily fine-grained and wrong—v.2.3 is better for me. Obviously, the ideal solution to support everyone's needs is to offer a choice for how finely to resolve ages.
Hi, This was a change that was intended for the iOS version that inadvertently got pushed to the Desktop version aswell. We will look to change it back for the next update, and will consider looking into using the precision of events to determine the precision of the age being displayed - for example only show years if you have just entered a birth year etc. Jess
As always, thanks for being responsive but ... did you mean "precision of events" or precision of _entities_? For my purposes, I would want the date-precision of the person entity, not the event he or she participates in, to determine the display of his/her age. An event may have a very specific date or date range, but the participants may need only show as _x_ years old.
Hi, I did mean events, not entities, but I actually meant the precision of the birth event/date, not all the events that the person is involved in. Sorry for the confusion, I should have explained that clearer. Jess
I think I follow you. That's actually one of the things I find hardest to get my head around with Aeon: Terminology. There are events such as birth & death within entities, as well as entities within events, and some of the things called entities don't really feel (to me) like entities, such as "Theme." I doubt I could come up with a better term than "entity" though; it's a consequence of Aeon's flexibility as a tool.
So glad to hear it was a mistake and will be fixed in the next version! I've only had a little time to use the newer version, but aside from this one little blip, I'm happy with it so far.