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 94
    • Issues 94
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 24
    • Merge Requests 24
  • 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
  • #163

Closed
Open
Opened May 24, 2020 by Kirill Chibisov@kchibisovContributor

Should the order of wl_keyboard::enter 'keys' be defined

Right now when client gains focus it receives the pressed keys via keys. So client has information that those keys are pressed and it could in theory restart repeat rate (not sure if anyone is doing that right now though), however since the order is not defined it has no idea what key to start repeating. Logically it seems like it should be the last pressed one, but there's no notion of the last pressed one. Compositor can in theory guarantee the order of those keys and place them in FIFO/LIFO order, so the client will know what it can repeat.

Alternatively you can say that clients must not start repeat from the keys in wl_keyboard::enter.keys.

cc @emersion since it was slightly touched on IRC.

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#163