mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-02-03 09:46:17 +01:00
gfile: More explicitly document the context for GFileProgressCallback
Be more explicit in the documentation for g_file_copy_async() about which GMainContext its progress callback is executed in. https://bugzilla.gnome.org/show_bug.cgi?id=728565
This commit is contained in:
parent
157521a5c4
commit
9352cdb5f4
@ -3402,8 +3402,9 @@ g_file_copy (GFile *source,
|
||||
* asynchronously. For details of the behaviour, see g_file_copy().
|
||||
*
|
||||
* If @progress_callback is not %NULL, then that function that will be called
|
||||
* just like in g_file_copy(), however the callback will run in the main loop,
|
||||
* not in the thread that is doing the I/O operation.
|
||||
* just like in g_file_copy(). The callback will run in the default main context
|
||||
* of the thread calling g_file_copy_async() — the same context as @callback is
|
||||
* run in.
|
||||
*
|
||||
* When the operation is finished, @callback will be called. You can then call
|
||||
* g_file_copy_finish() to get the result of the operation.
|
||||
|
Loading…
Reference in New Issue
Block a user