> > 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 :-|): http://cvs.gnome.org/viewcvs/evolution-data-server/calendar/tests/ecal/test-recur.c?rev=1.3&view=markup http://cvs.gnome.org/viewcvs/evolution-data-server/calendar/tests/ecal/test-search.c?rev=1.2&view=markup http://cvs.gnome.org/viewcvs/evolution-data-server/addressbook/tests/ebook/test-ebook.c?rev=1.6&view=markup Should I file a bug? Cheers, V. Seguí _______________________________________________ evolution-hackers maillist - [email protected] http://lists.ximian.com/mailman/listinfo/evolution-hackers
