Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G geoclue
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • geoclue
  • geoclue
  • Issues
  • #123

Closed
Open
Created Nov 18, 2019 by Zeeshan Ali@zeenixOwner

Distance & Timethreshold properties needed in GClueSimple

With !11 (merged) merged, we've a tiny bit of an issue: Any app that needs to set the threshold properties, will now get a crash as gclue_simple_get_client will now give them a NULL (where it was previously guaranteed). So we have 3 issues:

  1. Documenting this new behaviour.
  2. Add these properties on GClueSimple itself, so they are proxied to GClueClient in case of outside the portal or to the portal otherwise.
  3. Open issues about this on known users of this API (GNOME apps at least).

This issue is about 2.

Assignee
Assign to
Time tracking