Skip to content

GitLab

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

Open
Created Jul 11, 2020 by Uli Schlachter@psychonMaintainer
  • Report abuse
Report abuse

WIP: xcb_wait_for_special_event_with_timeout()

  • Overview 8
  • Commits 1
  • Changes 4

This surely has portability problems and is ugly since it works with three different representations (timeout in milliseconds, deadline as timeval, deadline as timespec).

Also, this is completely untested. But at least its a start.

Related to #38

Anyone who wants is free to pick this up and do it properly.

For the public API, I was thinking on whether this should be a timeout (as it is now) or a deadline (struct timeval / timespec). I only picked the timeout so that no structs from sys/time.h appear in the public API. No idea if that was a good choice.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: wait_for_special_event_with_timeout