Callbacks

	EnrollProgress (device, completed_stages, print_, user_data, error)
	MatchCb (device, match, print_, user_data, error)

Details

FPrint.EnrollProgress(device, completed_stages, print_, user_data, error)

Parameters:

• device (FPrint.Device) – a FPrint.Device

• completed_stages (int) – Number of completed stages

• print (FPrint.Print or None) – The last scanned print

• user_data (object or None) – User provided data

• error (GLib.Error or None) – GLib.Error or None

The passed error is guaranteed to be of type %FP_DEVICE_RETRY if set.

FPrint.MatchCb(device, match, print_, user_data, error)

Parameters:

• device (FPrint.Device) – a FPrint.Device

• match (FPrint.Print or None) – The matching print if any matched print

• print (FPrint.Print or None) – The newly scanned print

• user_data (object or None) – User provided data

• error (GLib.Error or None) – GLib.Error or None

Report the result of a match (identify or verify) operation.

If match is non-None, then it is set to the matching FPrint.Print as passed to the match operation. In this case error will always be None.

If error is not None then its domain is guaranteed to be %FP_DEVICE_RETRY. All other error conditions will not be reported using this callback. If such an error occurs before a match/no-match decision can be made, then this callback will not be called. Should an error happen afterwards, then you will get a match report through this callback and an error when the operation finishes.

If match and error are None, then a finger was presented but it did not match any known print.

print represents the newly scanned print. The driver may or may not provide this information. Image based devices will provide it and it allows access to the raw data.

This callback exists because it makes sense for drivers to wait e.g. on finger removal before completing the match operation. However, the success/failure can often be reported at an earlier time, and there is no need to make the user wait.