Skip to content

GitLab

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

Closed
Open
Opened Sep 04, 2014 by Bugzilla Migration User@bugzilla-migration

Document wl_proxy user data surprises

Submitted by Pekka Paalanen

Assigned to Wayland bug list

Link to original bug (#83479)

Description

People get surprised, that for a wl_proxy:

  • add_listener can only be used once, so it's more a "init", not "add"
  • add_listener sets the same user data as set_user_data does

Might as well review that all aspect of the user data are documented.

This should be both in the per-function doc comments picked up by Doxygen, and when a "big docs" chapter about the client side API gets started, there.

Blocking

  • Bug 83429
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: wayland/wayland#21