Last Comment Bug 304486 - moving a floating event puts it in the default timezone
: moving a floating event puts it in the default timezone
: dataloss
Product: Calendar
Classification: Client Software
Component: Internal Components (show other bugs)
: Trunk
: All All
-- normal (vote)
: Lightning 0.3
Assigned To: Joey Minta
Depends on:
Blocks: 321164
  Show dependency treegraph
Reported: 2005-08-12 12:54 PDT by Dan Mosedale (:dmose)
Modified: 2006-03-27 06:49 PST (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Dan Mosedale (:dmose) 2005-08-12 12:54:58 PDT
It's possible this is lightning-specific, but I suspect not.  Moving an event
that's scheduled in floating time by dragging it causes it to be put in the
default timezone.
Comment 1 User image Dan Mosedale (:dmose) 2005-12-13 15:40:27 PST
Presumably something similar happens for Zulu events.  For the moment, we'd like everything created in Lightning to be pinned to the default timezone.  However, any events in a file that have some other modality (floating, Zulu, pinned to another timezone) should preserve that modality when modified either by dialog or drag-n-drop.
Comment 2 User image Dan Mosedale (:dmose) 2006-01-27 13:02:40 PST
0.1 is now targetted at no dataloss on self-generated data.  Since we shouldn't be generating any floating events at the moment...
Comment 3 User image Joey Minta 2006-03-24 14:05:45 PST
I'm pretty sure the patch on bug 323696 will solve this.
Comment 4 User image Joey Minta 2006-03-27 06:49:55 PST
Fixed by bug 323696.

Note You need to log in before you can comment on or make changes to this bug.