254
264
klass->ask_password = ask_password;
255
265
klass->ask_question = ask_question;
256
266
klass->show_processes = show_processes;
267
klass->show_unmount_progress = show_unmount_progress;
259
270
* GMountOperation::ask-password:
373
384
G_TYPE_STRING, G_TYPE_ARRAY, G_TYPE_STRV);
387
* GMountOperation::show-unmount-progress:
388
* @op: a #GMountOperation:
389
* @message: string containing a mesage to display to the user
390
* @time_left: the estimated time left before the operation completes,
391
* in microseconds, or -1
392
* @bytes_left: the amount of bytes to be written before the operation
393
* completes (or -1 if such amount is not known), or zero if the operation
396
* Emitted when an unmount operation has been busy for more than some time
397
* (typically 1.5 seconds).
399
* When unmounting or ejecting a volume, the kernel might need to flush
400
* pending data in its buffers to the volume stable storage, and this operation
401
* can take a considerable amount of time. This signal may be emitted several
402
* times as long as the unmount operation is outstanding, and then one
403
* last time when the operation is completed, with @bytes_left set to zero.
405
* Implementations of GMountOperation should handle this signal by
406
* showing an UI notification, and then dismiss it, or show another notification
407
* of completion, when @bytes_left reaches zero.
409
* If the message contains a line break, the first line should be
410
* presented as a heading. For example, it may be used as the
411
* primary text in a #GtkMessageDialog.
415
signals[SHOW_UNMOUNT_PROGRESS] =
416
g_signal_new (I_("show-unmount-progress"),
417
G_TYPE_FROM_CLASS (object_class),
419
G_STRUCT_OFFSET (GMountOperationClass, show_unmount_progress),
422
G_TYPE_STRING, G_TYPE_INT64, G_TYPE_INT64);
376
425
* GMountOperation:username:
378
427
* The user name that is used for authentication when carrying out