Re: When do open_sync() gets called from a calendar backend?

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 that e_cal_open() is being called, not
e_cal_open_async(). My calendar inherits from ECalBackendSync so isn't
that as it should be?

Well, I'll better spread a few printf()'s in e_cal_open() to see where
it fails.

Thanks,
  jules



> thanks, Chenthill.
> 
> On Fri, 2006-05-05 at 14:05 +0200, Jules Colding wrote:
> > 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_timezone_sync() being invoked
> > (in that order).
> > 
> > The next thing to happen is that Evolution tells me that it is unable to
> > open the calendar.
> > 
> > Do I have to invoke open_sync() myself at some appropriate time? 
> > 
> > 
> > Thanks,
> >   jules
> > 
> > BTW: I have invoked e_cal_backend_sync_set_lock(backend, TRUE) in
> > e_cal_backend_brutus_init() to force serialization of method
> > invocations. 
> > 
> > _______________________________________________
> > Evolution-hackers mailing list
> > [email protected]
> > http://mail.gnome.org/mailman/listinfo/evolution-hackers