Summary | Embedded "Upcoming Events" view shows multi-day events once for each day |
Queue | Kronolith |
Queue Version | Git develop |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | pafcu (at) iki (dot) fi |
Created | 04/08/2012 (4807 days ago) |
Due | |
Updated | 08/29/2012 (4664 days ago) |
Assigned | |
Resolved | 04/14/2012 (4801 days ago) |
Milestone | |
Patch | No |
commit 4c57fb7eb70cef8567bf48fb9a1641bf7333a02c
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Sat Apr 14 12:46:52 2012 -0400
Don't show multiday events more than once in the Monthlist block.
Ticket: 11136kronolith/lib/Block/Monthlist.php | 25 ++++++++++++++++++-------
1 files changed, 18 insertions(+), 7 deletions(-)
http://git.horde.org/horde-git/-/commit/4c57fb7eb70cef8567bf48fb9a1641bf7333a02c
State ⇒ Resolved
commit 4c57fb7eb70cef8567bf48fb9a1641bf7333a02c
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Sat Apr 14 12:46:52 2012 -0400
Don't show multiday events more than once in the Monthlist block.
Ticket: 11136kronolith/lib/Block/Monthlist.php | 25 ++++++++++++++++++-------
1 files changed, 18 insertions(+), 7 deletions(-)
http://git.horde.org/horde-git/-/commit/4c57fb7eb70cef8567bf48fb9a1641bf7333a02c
State ⇒ Accepted
Priority ⇒ 1. Low
April
11.-15. Multiday event
13. Single day event in the middle of the above event
block which has headers, not prefixes for the individual days.
showing the wrong number of days for an event is a bug.
If maxevents does not, in fact, set the maximum number of events to
show, could the name be changed to something that reflects its use
better? Maybe "maxeventdays"?
Multiple events during a day can be shown e.g. like this:
April
11.-15. Multiday event
13. Single day event in the middle of the above event
If you are concerned that people think that the second event is after
the first one (instead of during) a special icon could be added to
turn attention to this.
The default could still be the old behaviour, but I think having an
option for this would be nice.
Here's my use case: I have lots of long 10-15 day events mixed with
lots of single day events (although they do not usually overlap). I
need to show entire events so people don't get confused (i.e. don't
show that a 15 day event is 2 days long), but at the same time it
looks bad to have 30 single day events listed in some cases (if I make
maxevents large enough to fit all the longer events).
It's also difficult to see single day events when they are "hidden"
between two long multiday events. At a glance, how many different
events are listed below?
1. My event a
2. My event a
3. My event a
4. My event a
5. My event a
6. My event a
7. My event a
8. My event a
9. My event a
10. My event a
11. My event c
12. My event d
13. My event d
14. My event d
15. My event e
16. My event f
17. My event f
18. My event f
19. My event f
Compare with:
1.-10. My event a
11. My event c
12.-14. My event d
15. My event e
16.-19. My event f
State ⇒ Not A Bug
because how would you render if you have both multi-day and single-day
events during the same days?
State ⇒ Unconfirmed
New Attachment: horde_bug.png
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Embedded "Upcoming Events" view shows multi-day events once for each day
Type ⇒ Bug
Priority ⇒ 2. Medium
multiple days is shown many times, once for each day. This is very
confusing, since it gives the impression that they are multiple
different events.
Instead of showing someting like:
July
1 Multi-day event
2 Multi-day event
3 Multi-day event
4 Multi-day event
5 Multi-day event
it should show
July
1 - 5 Mutli-day event
Since each day is shown as a separate event, this also breaks the
"maxevents" parameter, which not only will not show the desired amount
of separate events, but gives the false impression that a long
multi-day event is shortar than it is, because only "maxevents" days
are shown.
The attached image illustrates the problem (length of event is 5 days,
maxevents = 3)