On Do, 2011-03-31 at 10:59 +0200, Patrick Ohly wrote: > On Do, 2011-03-31 at 07:56 +0100, Alvaro Manera wrote: > > On Tuesday, March 29, 2011 05:35:04 pm ext Patrick Ohly wrote: > > * iCal support was faulty. Well yes it had some bugs, but most of them are > > closed only two are open and one assigned to you.
Forgot to comment on that: https://bugs.meego.com/show_bug.cgi?id=6049 is the meta bug where I described how to test iCalendar 2.0 import/export in MeeGo, before filing individual bug reports about every problem found that way. I'll close it once #6054 is resolved. In #6054 I asked about unexpected behavior in mKCal, which hasn't been answered yet. > > About the partial loading of mKCal. Is it faulty? Please provide the bug > > number. > > It was faulty: https://bugs.meego.com/show_bug.cgi?id=6061#c5 > > I still find it hard to use correctly. For example, which events need to > be loaded to get a correct response for "events falling into the time > range 2011-03-31 00:00 Europe/Berlin until 2011-03-31 23:59 > Europe/Berlin"? Which API calls, which parameters? Incidentally, that's the same question that I asked before in 6061#c5, without getting a reply. I'm still interested in the answer, so I hope we can discuss it now here on the list. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
