On 22 February 2011 19:53, Christian Becke wrote:
> Sorry, misread your message. The object is actually both: passed as an
> argument to the callback, and accessible through the gio.AsyncResult by
> calling its get_source_object method, see code below:
Right, I did wonder about the redundancy, bu
Am 22.02.2011 12:37, schrieb Christian Becke:
Am 22.02.2011 05:29, schrieb Jason Heeris:
I'm confused about some of the GIO async functions. In my case, I want
to use gio.File.replace_contents_async(). But what's the signature of
the callback it takes? I would assume that the callback receives t
Am 22.02.2011 05:29, schrieb Jason Heeris:
I'm confused about some of the GIO async functions. In my case, I want
to use gio.File.replace_contents_async(). But what's the signature of
the callback it takes? I would assume that the callback receives the
original File object, but looking at the doc
I'm confused about some of the GIO async functions. In my case, I want
to use gio.File.replace_contents_async(). But what's the signature of
the callback it takes? I would assume that the callback receives the
original File object, but looking at the docs for gio.AsyncResult, it
might also need to
