Hi Ben,
Yes, a code patch is possible but that’s a real drag for maintaining the code after each update. Also, we don’t always want inverse chronological order, only for certain pages. We also want to be able to list future events in ascending order.
In fact, we had patched the code to allow listing previous events going backwards from the current date. It’s because of the maintenance problems that poses that we have abandoned that.
When we want to list past events, we now use the “exact-date” possibility that you pointed out to us. However, it’s a workaround for us, since although maintainability is improved (we no longer have to re-patch the code for each new version), ergonomics of use is not. We always start from the oldest event (and then for forwards) rather than starting from the most recent past event (and going backwards).
It would be great if a future version could allow the user to choose, via a shortcode parameter, whether normal or inverse chronological ordering is required. The current date or the exact-date could still specify from what date to start listing events (in either order).
Just an idea to improve your otherwise splendid plugin.
— David