After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 165739 - gnome_vfs_async_xfer documentation is fuzzy
gnome_vfs_async_xfer documentation is fuzzy
Status: RESOLVED DUPLICATE of bug 93562
Product: gnome-vfs
Classification: Deprecated
Component: Docs
unspecified
Other Linux
: Low minor
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-30 20:54 UTC by Olivier Sessink
Modified: 2005-02-05 21:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Olivier Sessink 2005-01-30 20:54:51 UTC
the docs for gnome_vfs_async_xfer are somewhat fuzzy, I'll try to explain the
issues:

1) GnomeVFSAsyncXferProgressCallback is not linked (from the html docs), I
looked it up in the gnome-vfs-async-ops.h file. In that file it sais the
callback should always return 0, except if status is GnomeVFSXferErrorAction or
GnomeVFSOverwriteAction.

2) GnomeVFSXferProgressCallback is in the html docs, but without description

3) both callbacks return gint, it seems unlogical that both have to pass the
user descision to gnome_vfs, so what should the return value be for both of the
functions?

4) returning 0 by default (as written in gnome-vfs-async-ops.h) seems to abort
all transfer

5) it *seems* (after some debugging, and looking at nautilus code) that the
progress_sync_callback is the callback that should pass the user descision to
gnome_vfs (please check this first)
Comment 1 Olivier Sessink 2005-01-30 21:05:25 UTC
another (only slightly related) issue:
the html index does not show the async functions. You have to click 'file
operations' and click 3 times 'next' to get to those functions
Comment 2 Christian Kellner 2005-02-05 21:40:27 UTC

*** This bug has been marked as a duplicate of 93562 ***