On Thu, 2010-07-01 at 13:41 +0200, Christian Hilberg wrote:
On Thursday 01 Juli 2010 at 08:58:32 Milan Crha wrote:
Hi all,
I'm working on a way to be able to report detailed errors from
addressbook/calendar backends to UI, so users will be able to see
something more sensible than just
On Thu, 2010-07-01 at 08:58 +0200, Milan Crha wrote:
I'm working on a way to be able to report detailed errors from
addressbook/calendar backends to UI, so users will be able to see
something more sensible than just Other error message in Evolution.
This is bug report for this [1], which I'm
On Thu, 2010-07-01 at 14:42 +0200, Patrick Ohly wrote:
Will that break libebook and libecal APIs? The issue only mentions
backends, but the subject of your emails includes EBook and ECal.
Hi,
for EBook it is, all the async API there uses 'status' as an indicator
of the operation result
On Thu, 2010-07-01 at 14:57 +0200, Milan Crha wrote:
On Thu, 2010-07-01 at 14:42 +0200, Patrick Ohly wrote:
Will that break libebook and libecal APIs? The issue only mentions
backends, but the subject of your emails includes EBook and ECal.
Hi,
for EBook it is, all the async API
On Thu, 2010-07-01 at 14:57 +0200, Milan Crha wrote:
for EBook it is, all the async API there uses 'status' as an indicator
of the operation result in the async callback. I'm changing it to GError
too. I'm still on ECalBackend, but it seems some similar change will be
in ECal too, though I'm
