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 243622 - negative appointment length makes former end become start time
negative appointment length makes former end become start time
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 260606 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-05-25 02:24 UTC by Luke Hutchison
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luke Hutchison 2003-05-25 02:24:59 UTC
Moving events in the Calendar to another day resets their duration to 1
hour in Evolution 1.3.3.

Steps to reproduce the problem:
1. Create an event of duration 2 hours: e.g. drag mouse over the 2-hr
interval from 3pm to 5pm, then type an event name.
2. Double-click on the event
3. Change the date under Start Time to the next day (don't change the
time).  Click Save.
4. The event now has a duration of 1hr (3pm-4pm), on the next day.
5. Change the start time back to 5pm by dragging the end of the event box
downward.
6. Double-click on the event
7. Change the date under End Time back to the day before.  Click save.
8. The event now has a duration of 1hr on the day before, but the start
time is now 4pm (i.e. it goes from 4pm-5pm).

Reproducibility: Every time.

System: RH9.
Comment 1 André Klapper 2004-12-09 14:19:27 UTC
exactly the same in evolution-2.0.2.0.200411260600-0.snap.ximian.10.1.
Comment 2 André Klapper 2004-12-09 14:22:33 UTC
err...should add my comment.

the first part is a duplicate of bug 216535; but the second part
(former end time becomes start time) is still valid. therefore
changing subject to "negative appointment length makes former end time
become start time".
Comment 3 André Klapper 2004-12-11 00:18:50 UTC
*** bug 260606 has been marked as a duplicate of this bug. ***
Comment 4 Luke Hutchison 2006-02-06 05:11:03 UTC
Seems fixed in latest 2.5.x.