Re: [Evolution-hackers] Re: Strange console messages when accessing e-d-s through the libecal C API

> Well it should be reasonably obvious - for whatever reason - some call
> you're making isn't complete yet.  Even though YOUR call is complete, it
> may have triggered extra processing which isn't yet.  e.g. an
> asynchronous signal may be pending as a result of the process.  A sleep
> or whatever lets it finish.

This makes sense withe the previous post by Chris, e.g., there is a
sync api for accessing (which runs a bonobo_main loop) e-d-s which
must be used by people who don't want to run a main_loop, and this
backend may not shutdown as it should.

> Maybe it's just a bug in eds libraries then, or maybe you need to call
> something to 'init' them.

I think it could be a bug, albeit harmless, in eds. The following
simple e-d-s tests I have tried do have this behaviour of printing the
message (I should have started trying that, my fault :-|):

Should I file a bug?

  V. Seguí

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]