On Mon, 2006-05-08 at 14:35 +0200, Jules Colding wrote:
> Hi Chenthill,
>
> On Sat, 2006-05-06 at 15:06 +0530, Chenthill wrote:
> > Hi Jules,
> > Once the mode and timezone is set, e_cal_open_async would be called to
> > open the calendar. Please check if e_cal_open_async is being called from
Hi Chenthill,
On Sat, 2006-05-06 at 15:06 +0530, Chenthill wrote:
> Hi Jules,
> Once the mode and timezone is set, e_cal_open_async would be called to
> open the calendar. Please check if e_cal_open_async is being called from
> evolution. You need not invoke it separately.
Hmm... I can see
Hi Jules,
Once the mode and timezone is set, e_cal_open_async would be called to
open the calendar. Please check if e_cal_open_async is being called from
evolution. You need not invoke it separately.
thanks, Chenthill.
On Fri, 2006-05-05 at 14:05 +0200, Jules Colding wrote:
> Hi,
>
> I a
Hi,
I am a bit mystified, due to my lack of intellectual resources, about
the behavior of my calendar backend.
I have created the gconf source for the calendar and are trying to get
Evolution to call open_sync() on it, but that never happens. Instead I
am seeing set_mode_sync() and set_default_ti