Closed Bug 285033 Opened 20 years ago Closed 19 years ago

unifinder should show occurences, not events

Categories

(Calendar :: Sunbird Only, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mvl, Assigned: mvl)

References

Details

(Keywords: regression)

Attachments

(1 file)

The event unifinder should display the occurences of event in the selected period, and not only look at events. The problem with this is when 'all events' is selected. That can't be done for events that recur forever. A possible solution would be to show only the first occurence. (and maybe somehow show that there are other occurences?)
Blocks: 281716
Yes, I'm being picky, but bug 271248 (as yet unconfirmed) listed this first, and does do so with more detail. Either way, one of them should be sorted out as a duplicate.
THis bug is about a current regression on trunk. And while working on that, we might as well think about what bug 281716 describes. So not a duplicate.
I wanted to say bug 271248. And the regression is that recurence of events is currently totally ignored, while it used to show the first occurence in the given time period.
Based on my limited testing, the storage provider's getItems() function is broken: it doesn't return only Events when only Events are requested. It always returns ocurrences. I have a patch that fixes that: after that, the unifinder works properly for displaying recurring events in that when choosing "All Events", only the first of the recurring event(s) are shown. Hmm. I shall open another bug for the broken storage provider getItems
Keywords: regression
Blocks: 288925
Attached patch patch v1Splinter Review
This patch add a filter to get occurances to the unifinder for all but 'all events'. I'm not really happy with it, but i think it is an improvement. It is inconsistent, but i think it is more useful to see the events this week etc that i'm willing to sacrifice consitency. Once this lands i will file a new bug to search for a better solution. Or maybe that solution won't be needed if we ever switch to lightnings calendar tree.
Assignee: mostafah → mvl
Status: NEW → ASSIGNED
Attachment #187356 - Flags: first-review?(pavlov)
Blocks: 298936
Attachment #187356 - Flags: first-review?(pavlov) → first-review?(jminta)
Comment on attachment 187356 [details] [diff] [review] patch v1 Looks good. Perhaps we can have a (hidden?) pref for 'If event always recurs, show next N events.' That's still not ideal though.
Attachment #187356 - Flags: first-review?(jminta) → first-review+
Comment on attachment 187356 [details] [diff] [review] patch v1 Looks good. Perhaps we can have a (hidden?) pref for 'If event always recurs, show next N events.' That's still not ideal though.
marking this one fixed. filed bug 299651 about the all events problem.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
QA Contact: gurganbl → sunbird
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: