1. 20 Oct, 2015 1 commit
  2. 08 May, 2015 1 commit
  3. 31 Mar, 2015 1 commit
    • Mika Allan Rauhala's avatar
      Adapt to KDecoration API changes · 3389c756
      Mika Allan Rauhala authored and Martin Flöser's avatar Martin Flöser committed
      Adapt to API changes introduced by b62e8888cd39301e00ad98dfe791fa66676408fb.
      It adds DecoratedClient::color(group, role) for getting colors that are
      not included in QPalette. Breeze used to read these colors from
      kdeglobals, breaking per window color schemes. KWin now handles reading
      these colors along with QPalette loading with DecorationPalette.
      REVIEW: 122883
  4. 08 Jan, 2015 1 commit
  5. 02 Dec, 2014 3 commits
  6. 11 Nov, 2014 2 commits
  7. 23 Oct, 2014 1 commit
  8. 21 Oct, 2014 1 commit
  9. 25 Jul, 2014 4 commits
    • Martin Flöser's avatar
    • Martin Flöser's avatar
      Implement borderingScreenEdges for the DecoratedClientImpl · a903fb2c
      Martin Flöser authored
      Uses the QuickTileMode of the Client to indicate which borders to
      remove. This could be extended to be in general when a window borders
      the screen edge and not just for quick tile mode.
    • Martin Flöser's avatar
      Destroy DecorationRenderer in setup/finish compositing · c8c0bace
      Martin Flöser authored
      So far the DecorationRenderer got destroyed and recreated after
      the signal compositing toggled was emitted. But that's too late for
      e.g. the OpenGL Textures to be destroyed. So lets trigger the destroy
      directly in setup/finish compositing. The new renderer will still be
      created after the compositing toggled is emitted - we don't want to
      have it recreated for the still active compositer type.
    • Martin Flöser's avatar
      Initial import of support for new KDecoration2 based decorations · 0030eb7f
      Martin Flöser authored
      NOTE: this is not working completely yet, lots of code is still ifdefed
      other parts are still broken.
      The main difference for the new decoration API is that it is neither
      QWidget nor QWindow based. It's just a QObject which processes input
      events and has a paint method to render the decoration. This means all
      the workarounds for the QWidget interception are removed. Also the paint
      redirector is removed. Instead each compositor has now its own renderer
      which can be optimized for the specific case. E.g. the OpenGL compositor
      renders to a scratch image which gets copied into the combined texture,
      the XRender compositor copies into the XPixmaps.
      Input events are also changed. The events are composed into QMouseEvents
      and passed through the decoration, which might accept them. If they are
      not accpted we assume that it's a press on the decoration area allowing
      us to resize/move the window. Input events are not completely working
      yet, e.g. wheel events are not yet processed and double click on deco
      is not yet working.
      Overall KDecoration2 is way more stateful and KWin core needs more
      adjustments for it. E.g. borders are allowed to be disabled at any time.