1. 09 Jul, 2020 1 commit
  2. 07 Jul, 2020 1 commit
  3. 04 Jul, 2020 1 commit
  4. 25 Jun, 2020 6 commits
    • Ismael Asensio's avatar
    • Ismael Asensio's avatar
      [kcm/kwinrules] Fix types property for NET::AllTypesMask · 8b9472e0
      Ismael Asensio authored
      When the user selects all of the types or none of them, the "types"
      property must be set to a special value (`NET::AllTypesMask = -1`),
      different than the sum of all the flags together.
      This re-implements this behaviour as the old KCM, fixing some heuristics
      that prevented finding the rule corresponding to the current window.
      The enum name that handles this property has been changed to `NetTypes`
      to make it more explicit.
      BUG: 423214
      FIXED-IN: 5.19.3
      TEST PLAN:
      1. Open the `Application specific settings` on a window via menu
      2. Select every "Window Type" (or none of them)
      3. Give the rule a different name than the default and save
      4. Open it again and check that the same rule is found
    • Vlad Zahorodnii's avatar
    • Vlad Zahorodnii's avatar
      [x11] Force FocusIn events for already focused windows · a0c4a8e7
      Vlad Zahorodnii authored
      Depending on the current focus stealing prevention level, it's possible
      for kwin to call XSetInputFocus() on a window that already has the input
      focus. In which case, we won't receive the corresponding FocusIn event
      and the client will remain inactive from kwin's perspective even though
      it isn't.
      In order to work around this issue, we can move the input focus to the
      null window. By doing so, it's guaranteed that we're going to receive
      the matching FocusIn event for the client.
      This commit indirectly fixes a bug where fullscreen games are displayed
      below panels.
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · 6a42eccf
      Script Kiddy authored
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · b62f687c
      Script Kiddy authored
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
  5. 24 Jun, 2020 3 commits
    • Ismael Asensio's avatar
      [kcm/kwinrules] Fix detection of wmclass property · 3bfc750a
      Ismael Asensio authored
      Property `wmclass` of a window rule works in a special way, as it can have
      two meanings depending on `wmclasscomplete` flag:
      - false: only matches `resourceClass`
      - true: matches `resourceName` and `resourceClass`
      This MR fixes two subtle bugs when detecting the properties of a window:
      In the first case, `resourceName` was being wrongly set instead, which
      prevented window matching for windows where those two values differ.
      Also, the `wmclass` field was always set to `resourceName` independently
      of `wmclasscomplete` property.
      BUG: 423138
      FIXED-IN: 5.19.3
    • Vlad Zahorodnii's avatar
      [x11] Hold a passive grab on buttons only when needed · ec5a0249
      Vlad Zahorodnii authored
      Due to a bug in the XI2 protocol, clients have to reset scroll valuators
      on XI_Enter because the scroll valuators might have changed while the
      pointer was elsewhere. The XI_Enter event is usually sent when an input
      device enters the window, but it can also be generated by a passive grab.
      If an XI_Enter event has been generated by a passive grab, the client
      should not reset scroll valuators. Unfortunately, there is no any
      reliable way for the client to determine if an XI_Enter event has been
      sent in response to a deactivated passive grab. A correct fix for the
      scroll issues in GTK apps would involve changes in the XI2 protocol.
      As a work around, we can hold a passive grab only if the current mouse
      wheel action is either "Activate and scroll" or "Activate, raise, and
      BUG: 394772
      FIXED-IN: 5.19.3
    • Cyril Rossi's avatar
      KCM KWin Decoration : kcfgc File attribute should point to kcfg file · 170741c4
      Cyril Rossi authored
      BUG: 423398
      FIXED-IN: 5.19.3
  6. 23 Jun, 2020 1 commit
  7. 22 Jun, 2020 2 commits
    • David Edmundson's avatar
      Fix build with loadThemeCursor templates · 34c1bccd
      David Edmundson authored
      WaylandCursorImage::loadThemeCursor(const T &shape) uses templates.
      These templates are used by input.cpp but the deifnition is in
      On some setups this creates a compilation problem.
      This patch introduces an explicit non-templated declaration with the
      defintion explicitly complied into the same class.
      In master this has been refactored away anyway, so this is a minimal
      patch to make things working in the least invasive way.
      BUG: 423052
    • Benjamin Port's avatar
      KCM Compositing: Fix save state · a8979aa4
      Benjamin Port authored
      use settings objects to track state instead of a class member that will need to be synchronized.
      BUG: 423223
  8. 20 Jun, 2020 1 commit
  9. 18 Jun, 2020 3 commits
  10. 17 Jun, 2020 5 commits
  11. 16 Jun, 2020 1 commit
  12. 11 Jun, 2020 1 commit
  13. 10 Jun, 2020 1 commit
    • Ismael Asensio's avatar
      [kcm/kwinrules] Fix slow scrolling through rules list · e307038f
      Ismael Asensio authored
      Every `AbstractItemDelegate` was instantiating a `Kirigami.ActionToolBar`,
      which is a very expensive component, rising CPU usage specially on long lists.
      Use `Kirigami.SwipeListItem` instead, as is seems the proper component.
      BUG: 421537
  14. 09 Jun, 2020 1 commit
  15. 07 Jun, 2020 2 commits
  16. 03 Jun, 2020 3 commits
  17. 02 Jun, 2020 3 commits
  18. 01 Jun, 2020 1 commit
  19. 31 May, 2020 2 commits
  20. 30 May, 2020 1 commit