Currently (Version 1.0.0-preview.40), an event containing pictures from various years seems to be getting assigned a random year (or is it the mean?). Can this be changed to display the range of years?
Example: I created an event with pictures from 2011, 2018 and 2020. However the event shows 2015.
Sorting the event on the timeline will need another thought. Maybe let the user pick the sorting year?
Currently (Version 1.0.0-preview.40), an event containing pictures from various years seems to be getting assigned a random year (or is it the mean?).
This is right, it’s the year of the mean capture date of the contained photos. As far as sorting goes, I think this is the overall best choice. Using the newest photo would be an alternative that may seem to behave more predictable, but can easily lead to unexpected results, for example when an edited photo gets the current date, instead of the original capture date, assigned by the photo editor.
But definitely, assigning a single date to an event is generally sub optimal. I’ve found a year next to the event name only in the search bar. The only place where I’ve found the year next to the event name was in the search bar. Do you have any other place in mind that I may have overlooked?
In any case, I’ve improved the search logic to show a date range there when applicable (will be in the next release).
Sorting the event on the timeline will need another thought. Maybe let the user pick the sorting year?
The current idea is that you’d pin any events of this nature to the top of the list, where they are then sorted by name instead of by date. It will also still appear in the assigned year section, but at least it can be found easily.
We also have the rough plan to allow different sorting modes for the event list, using properties other than year or name, which would open up alternative approaches for dealing with this. Manually selecting a year could be a possibility, too, but it kind of goes against the idea of letting the application automate repeated work where possible, so I’m a bit reluctant going that route.