1. 12 Feb, 2020 4 commits
    • Vlad Zahorodnii's avatar
      [effects/desktopgrid] Use windowFrameGeometryChanged · f7891ee2
      Vlad Zahorodnii authored
      Summary:
      Use windowFrameGeometryChanged rather than windowGeometryShapeChanged
      because we are interested only in frame geometry changes.
      
      Reviewers: #kwin, davidedmundson
      
      Reviewed By: #kwin, davidedmundson
      
      Subscribers: kwin
      
      Tags: #kwin
      
      Differential Revision: https://phabricator.kde.org/D26908
      f7891ee2
    • Vlad Zahorodnii's avatar
      [effects/snaphelper] Use windowFrameGeometryChanged · b3b5a548
      Vlad Zahorodnii authored
      Summary:
      Use windowFrameGeometryChanged rather than windowGeometryShapeChanged
      because we are interested only in frame geometry changes.
      
      Reviewers: #kwin, davidedmundson
      
      Reviewed By: #kwin, davidedmundson
      
      Subscribers: kwin
      
      Tags: #kwin
      
      Differential Revision: https://phabricator.kde.org/D26909
      b3b5a548
    • Vlad Zahorodnii's avatar
      Expose frameGeometryChanged signal to effects · 00f4f88f
      Vlad Zahorodnii authored
      Reviewers: #kwin, davidedmundson
      
      Reviewed By: #kwin, davidedmundson
      
      Subscribers: davidedmundson, kwin
      
      Tags: #kwin
      
      Differential Revision: https://phabricator.kde.org/D26864
      00f4f88f
    • Vlad Zahorodnii's avatar
      Introduce Toplevel::frameGeometryChanged signal · 15af09c7
      Vlad Zahorodnii authored
      Summary:
      Currently we have two signals that are emitted when the Toplevel's geometry
      changes - geometryShapeChanged() and geometryChanged(). The former signal
      is used primarily to invalidate cached window quads and the latter is
      sort of emitted when the frame geometry changes. But it's not that easy. We
      have a bunch of connects that link those signals together...
      
      The worst part about all of this is that the window quads cache gets
      invalidated every time a geometry update occurs, for example when user
      moves a window around on the screen.
      
      This change introduces a new signal and deprecates the existing geometryChanged
      signal. frameGeometryChanged is similar to geometryChanged except that it is
      emitted when an _actual_ geometry change has occurred.
      
      We do still emit geometryShapeChanged signal. However, in long term, we
      need to get rid of this signal or come up with something that makes sense
      and doesn't require us to waste computational resources.
      
      Reviewers:...
      15af09c7
  2. 11 Feb, 2020 4 commits
    • Vlad Zahorodnii's avatar
      Merge branch 'Plasma/5.18' · dd96e444
      Vlad Zahorodnii authored
      dd96e444
    • Vlad Zahorodnii's avatar
      [libkwineffects] Detect more AMD GPUs with GFX9 (Vega) chips · b94a78c4
      Vlad Zahorodnii authored
      Summary: ASIC family names are taken from Mesa's source code.
      
      Test Plan: Compiles.
      
      Reviewers: #kwin, davidedmundson
      
      Reviewed By: #kwin, davidedmundson
      
      Subscribers: davidedmundson, romangg, kwin
      
      Tags: #kwin
      
      Differential Revision: https://phabricator.kde.org/D27176
      b94a78c4
    • Vlad Zahorodnii's avatar
      Put the resize effect in charge of scheduling repaints · 2f506cd3
      Vlad Zahorodnii authored
      Summary:
      If the frame geometry is changed in any away, for example if the client
      has been moved, resized, or both, setFrameGeometry() will schedule a layer
      repaint for the visible geometry before and after the update.
      
      When there is a resize effect, we only send requests to the client window
      to render contents at the new size. setFrameGeometry() is not called and
      therefore no layer repaints are scheduled.
      
      Only the resize effect knows what parts of the window or the screen must
      be repainted and thus it must be responsible for scheduling repaints.
      
      A full repaint in AbstractClient::performMoveResize() is scheduled mostly
      for historical reasons.
      
      Reviewers: #kwin, davidedmundson
      
      Reviewed By: #kwin, davidedmundson
      
      Subscribers: davidedmundson, kwin
      
      Tags: #kwin
      
      Differential Revision: https://phabricator.kde.org/D27167
      2f506cd3
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · 78c0095a
      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"
      78c0095a
  3. 09 Feb, 2020 2 commits
  4. 08 Feb, 2020 2 commits
    • Heiko Becker's avatar
      7d8a7e70
    • Heiko Becker's avatar
      Require kdecoration >= 5.18.0 · 6d8f3732
      Heiko Becker authored
      Summary:
      To successfully build kwin needs 13e6459a3baeebe6a7b594efd995b88f6dd7524e
      in kdecoration. Otherwise it fails with: "previewclient.h:93:11: error:
      'QSize KDecoration2::Preview::PreviewClient::size() const' marked
      'override', but does not override QSize size() const override;"
      So this is not a new requirement but just an update to the build system
      to reflect the actual requirements.
      
      Test Plan: Builds fine with the newly required version
      
      Reviewers: #kwin
      
      Subscribers: kwin
      
      Tags: #kwin
      
      Differential Revision: https://phabricator.kde.org/D27242
      6d8f3732
  5. 06 Feb, 2020 5 commits
  6. 05 Feb, 2020 3 commits
  7. 03 Feb, 2020 9 commits
  8. 31 Jan, 2020 3 commits
  9. 29 Jan, 2020 8 commits