Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
L
libfprint
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libfprint
  • libfprint
  • Issues
  • #119

Closed
Open
Created Oct 23, 2018 by Bastien Nocera@hadessOwner

Rework public async API

Right now, (nearly all) the async _start() calls require using a callback, and calling the appropriate _finish() function. Ideally, those would be called automatically when the operation has finished, and the _finish() call would only be needed to capture the result, not to set the fingerprint driver's state machine back in the right state.

This would make the async functions similar to GIO's "GTask" handling.

Benefits:

  • Generic callbacks for finished operations (but new callbacks for enrollment progress)
  • Less confusion for front-end developers
  • Clearer match between sync/async, and when to call _finish()
Assignee
Assign to
2.0
Milestone
2.0
Assign milestone
Time tracking
None
Due date
None