Hi Andre, I'm cc:ing the design list with this because I imagine other people will be seeing this behavior.
Thanks for finding this, it's a kind of complicated collection of different bugs. 1) The first time Chandler serializes an anytime event, it gets it right, but later serializations are wrong (I just fixed that) 2) Cosmo doesn't actually handle anytime events well, yet, it displays them as timed events at midnight So what's happening is that your lone midnight event is actually a correctly serialized anytime event (not yet handled by Cosmo). The identical item in the other collection isn't quite identical because it was serialized by Chandler twice. Bobby has bug 8217, let Cosmo tolerate Chandler's buggy output. Since they're now the default, anytime events are likely to be used more now in Chandler. Folks should be prepared for them to (temporarily) not render quite right in Cosmo. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
