After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 440184 - Gnome clock applet does not display multi-days event from evolution correctly
Gnome clock applet does not display multi-days event from evolution correctly
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: clock
2.19.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-21 14:21 UTC by Sebastien Bacher
Modified: 2007-05-21 21:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
fix the bug (967 bytes, patch)
2007-05-21 14:26 UTC, Sebastien Bacher
none Details | Review
updated version according to Vincent comment (952 bytes, patch)
2007-05-21 21:16 UTC, Sebastien Bacher
committed Details | Review

Description Sebastien Bacher 2007-05-21 14:21:37 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/114515

"A small regression from Edgy to Feisty : the clock calendar pop-up shows multi-days event defined in evolution as one day event (only the first day in bold) even if the bottom panel of the calendar correctly shows the event for all consequent days).

http://librarian.launchpad.net/7619609/cal.png
cal.png"
Comment 1 Sebastien Bacher 2007-05-21 14:26:58 UTC
Created attachment 88549 [details] [review]
fix the bug

The bug has been introduced with http://svn.gnome.org/viewcvs/gnome-panel?view=revision&revision=10180. The new patch makes it make all the days untill the duration is reached (which is n* 86400).

I've tested the change with one all day event, one multi-days event, one normal event on on e day and another spawing on an another days, they are all displayed correctly
Comment 2 Vincent Untz 2007-05-21 19:28:30 UTC
Doesn't this patch reintroduce bug 305022? The code you propose does the same thing as the code before the fix for bug 305022.
Comment 3 Sebastien Bacher 2007-05-21 20:31:10 UTC
Not, it's not, supposing the other bug happens in the case when the event doesn't spaw on the day.

Take the example of a duration = 100 000 = 1.16 days, 2 days have to be marked on the calendar)

duration / 86400 = 1 (that's an int division),

* code before 305022
day_offset < 1 is not true so there is no extra day marked, which was the bug

* code now
day_offset <= 1, one extra day is marked

* the patched version
day_offset <= 1
100 000 != 86400 * 1
one extra day is marked


The thing is that the duration / 86400 = 1 when 86400 <= duration < 172799, but we don't want to add a day when it's = 86400 (which is exactly one day), that's the case the suggest patch is changing 
Comment 4 Sebastien Bacher 2007-05-21 21:16:42 UTC
Created attachment 88565 [details] [review]
updated version according to Vincent comment

I've commited this version