This week in KWin (2012, week 34)

This week we have mostly seen work on 4.10 and not so much on 4.9.1. Two further bugs in Window Switching got fixed and a few more bug fixes are in the pipeline (I have a small review backlog).

But the work on 4.10 is rather impressive and really important. First of all I want to thank Jammy Zhou for adapting our OpenGL test application to determine whether the Catalyst driver supports direct rendering with compositing. Thanks to that change KWin will default to direct rendering and OpenGL 2 on the latest Catalyst drivers (in fact KWin defaults to direct rendering on all drivers now). If you are already using a recent Catalyst version you can also set the environment variable “KWIN_DIRECT_GL” to “1″ to enforce direct rendering, no matter what the test app thinks. This works with all currently supported KWin versions.

My work concentrated on finishing the Plastik port to QML which I just merged into master. The classic decoration is still around, I want to make sure that the QML port is working correctly first. Please give it a try with e.g. Project Neon.

Furthermore I did quite some refactoring. Last week I mentioned the addition of Screens to the “User actions Menu” and that actually triggered some working on that code as I realized that this needs to be split out. This refactoring got just merged, too. And last but not least, I finally finished some unmerged work from last year GSoC. We again and again broke the patch set which made it difficult to merge. The user actions menu which I merged first, caused serveral merge conflicts again, so that was not a trivial thing. I intend to do a dedicated blog post to explain the refactoring especially as I have some more work already prepared. The numbers of these three merged branches today are quite impressive:

21 files changed, 650 insertions(+), 353 deletions(-)
7 files changed, 812 insertions(+), 555 deletions(-)
36 files changed, 2509 insertions(+), 160 deletions(-)

Summary

Crash Fixes

    Bug Fixes

    • 305449: Empty TabBox in case of no active Client
      This change will be available in version 4.9.1
      Git Commit
    • 304950: alt+tab works wrong with “one window per application”
      This change will be available in version 4.9.1
      Git Commit

    New Features

    • 301327: Option to disable close on double click in Aurorae
      This change will be available in version 4.10
      Git Commit
    • 301103: Allow direct rendering with fglrx
      This change will be available in version 4.10
      Git Commit
    • 303810: Generic QML support for Aurorae Themes
      This change will be available in version 4.10
      Git Commit

    Tasks

    • 299277: Move Workspace’s compositing functionality to own class Compositor
      This change will be available in version 4.10
      Git Commit
    • 305832: Split out Useractions Menu from Workspace
      This change will be available in version 4.10
      Git Commit

    10 thoughts on “This week in KWin (2012, week 34)

    1. [quote]
      I intend to do a dedicated blog post to explain the refactoring especially as I have some more work already prepared.
      [/quote]

      Please do! That kind of stuff is always interesting to read :)

      [quote]
      305832: Split out Useractions Menu from Workspace
      This change will be available in version 4.10
      [/quote]

      Does this mean that the rmb content menu from decorations will now look exactly the same as a rmb on the desktop? Asking this since there was some visual difference before (no shadow?) because the rmb menu for decorations was done in a special way iirc. Or am i mixing some things up now?

      1. You are mixing things up. It’s not possible to have the same menu as the one is for windows and the other for tasks. So it’s not exactly the same thing (there are more reasons why it’s not possible).

        But shadow is working here for me everywhere :-)

        1. Ahh oke (oke, not shadows, but something was different in there compared to menus handled outside of kwin).

          Would you mind doing a post about that subject? It’s kinda difficult stuff but at the same time very interesting!

          Cheers and keep up the awesome work!

    2. These blogs are a “must read” as they provide such good info and let us,, the regular users, know what is happening and what to expect. I can’t thank Martin enough for doing hi8s blogs.

    3. May be I am little naive and or little demandig. I was struggling with getting a default resolution set properly on AMD computer at my home. Is it possible that it can be addressed by such updates from driver manufacturer and your combined effort.

      I discussed this issue in the forum and just putting the link for reference.
      http://forum.kde.org/viewtopic.php?f=17&t=96570

      Apology in advance if ettiquette is not followed properly.

        1. In case you have some idea, kindly advise me how to go about addressing this issue. It may look trivial to you, but I could not figure it out. I am not very familiar to computer architecture and chemist by profession. Still use kubuntu as my OS for office and home desktops.

    Comments are closed.