Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • KWin KWin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 57
    • Issues 57
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 156
    • Merge requests 156
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PlasmaPlasma
  • KWinKWin
  • Issues
  • #19
Closed
Open
Issue created Oct 26, 2020 by Vlad Zahorodnii@vladzDeveloper

Introduce X11-specific and Wayland-specific sets of input event filters

On Wayland, features such as window actions and move/resize are implemented using generic input event filters. They work for all kinds of clients, e.g. XdgToplevelClient, InternalClient, etc.

The problem is that X11Client/XwaylandClient implements window management features as well using X11-specific stuff, which may conflict with the event filters.

In order to resolve that conflict, we need to introduce X11-specific and Wayland-specific sets of event filters and use only one of them based on whether we're running as a wayland compositor or as an x11 window manager.

Assignee
Assign to
Time tracking