Re: [PATCH] Improve GnomeVFS XFer code (was: Re: [PATCH] Improve Nautilus XFer code)



Am Mittwoch, den 11.01.2006, 18:33 +0100 schrieb Christian Neumair:
> Am Mittwoch, den 11.01.2006, 15:38 +0100 schrieb Alexander Larsson:
> > The async callback is used for slower, ui handling. Its where you
> > handle
> > errors, and progress updates. Its *always* called on errors or other
> > "must be handled by user" cases (name conflicts, etc), but its only
> > periodically called when it comes to "normal" progress so that you can
> > update a progress bar without slowing down the app to a crawl.
> 
> OK, now I grasp it. The attached patch makes GnomeVFS force the call to
> the async callback whenever the value is not just interpreted as bool
> but does form some kind of decision possibly done by the user.

Sorry, it turns out that this can't be the reason for the problems,
because GNOME_VFS_XFER_OVERWRITE_ACTION_ABORT is 0.
Sorry for all this bugzilla, mailing list and blog spam.

-- 
Christian Neumair <chris gnome-de org>

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil



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