Recurring Evolution events not shown as coming events in clock's menu

A recurring event like this can clutter the calendar if there are no other events in the calendar as well; however, I don't see any discussion of this in the spec so I don't know if Design considered this case. Reassigning to mpt.

I did not consider this case. It would be extremely rare, since the list should include only events for the selected day, and events hardly ever repeat more than once a day.

But as long as the overall maximum number of events is adhered to, I don't think it's a problem that the list might include multiple occurrences of the same event. On the contrary, if they are omitted, you might not realize that some other event clashes with a recurrence.

Specification updated. <https://wiki.ubuntu.com/TimeAndDate?action=diff&rev2=110&rev1=109>

On 2016-01-19 16:52, Matthew Paul Thomas wrote:
> I did not consider this case. It would be extremely rare, since the
> list should include only events for the selected day, and events
> hardly ever repeat more than once a day.

Not sure what you mean by that, Matthew. The case which made me observe this bug was an event which recur every fourth week. The list shows the next five events (or so) from the day you select, and it's certainly not limited to events for the selected day. When selecting a day soon before the day of the second (or third...) instance of the recurring event, it was simply skipped.

I have been using the event list in the clock as a planning tool for a while, and because of this bug I was about to forget about this recurring event.

> Specification updated.
> <https://wiki.ubuntu.com/TimeAndDate?action=diff&rev2=110&rev1=109>

I now see that the limitation to "for the selected day" you mention was added on 2015-05-11 in revision 100 of the specifitation. It hasn't been implemented yet AFAICT for regular events.

Personally I consider this change to the spec. to be an important regression bug, and for me it's going to make the list more or less useless as a planning tool.

I would strongly suggest that the spec is changed again, so the list is designed to show "the next five calendar events, if any" as was the case before revision 100.

I'm sorry I misunderstood the original report. It would have helped if it had contained steps to reproduce the problem.

If you select the date of a recurrence that isn't the next recurrence, and the event doesn't show up in the list, then that's a bug *regardless* of whether the list should include events from other days. If that, separate, issue was your motivation for setting this bug report to High importance, that may be misguided.

On the subject of including events from other days, my objection to that would have been that it would be weird to show events from the date you selected and also events from dates that *weren't* the date you selected. However, I've just realized that I was trying to be too clever in saying that the list should be of "events for the selected day", for two reasons. First, the list of events might be present while the calendar is not present at all. Secondly, as specified, choosing a date opens the calendar app to that date, which naturally closes the menu. It can't do both that *and* show you a list of events underneath. (Conceivably it could show a date's events when the date is highlighted (moused over or arrowed to), and open the calendar when the date is chosen (clicked or Enter pressed). Or we could show a date's events when the date is chosen, and (as seems to be implemented now) open the calendar on a double-click. But neither would work when keyboard navigation is implemented properly. The former wouldn't work because arrowing towards the list of events would change the selected date, which would make the events you were trying to navigate to disappear; and the latter wouldn't work because there's no keyboard equivalent to a double-click.)

So, as you suggested, I've reverted that change. The list should show upcoming events, regardless of whether the calendar above is present or what you do with it. <https://wiki.ubuntu.com/TimeAndDate?action=diff&rev2=111&rev1=110>

Here is an event that causes this behavior for me.

BEGIN:VEVENT
UID:20151108T020045Z-4971-1001-2621-1@roku
DTSTAMP:20160401T184310Z
CREATED:20151108T020045Z
RRULE:FREQ=WEEKLY;UNTIL=20160630;BYDAY=WE
LAST-MODIFIED:20160401T184310Z
SUMMARY:Rotary
DTSTART;TZID=America/Chicago:20150701T120000
DTEND;TZID=America/Chicago:20150701T130000
LOCATION:First United Methodist Church\, Allen\, TX
EXDATE:20150826T120000
EXDATE:20151125T120000
EXDATE:20151021T120000
EXDATE:20151118T120000
EXDATE:20151028T120000
EXDATE:20151104T120000
EXDATE:20151223T120000
EXDATE:20151230T120000
EXDATE:20160120T120000
CLASS:PUBLIC
EXDATE:20160420T120000Z
END:VEVENT