Hello! Let me share an observation, just in case that it is relevant for other developers. mkcal supports multiple "notebooks" inside the same calendar database. However, these notebooks are not as independent from each other as one might expect: if notebook A has an event with UID=foo, then notebook B cannot also have an event with that same UID.
I suppose this works as intended, but it is not how other PIM storages work. I also find it a too limiting and wonder how this feature is used. If one notebook is say, synchronized with Google, and the other notebook is for a local calendar, then I would get conflicts when a meeting invitation is processed by both Google and the local app. The only solution that I see is to not use the "notebook" feature and instead use separate calendar .db files. Alvaro, do I miss something? -- 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 [email protected] http://lists.meego.com/listinfo/meego-dev
