EDGECASES, EDGECASES, EDGECASES!

Doesn’t tile properly when screen disappears

Resolution changes

Almost possible, but clientArea returns the old resolution

Testing

Weird apps (mplayer, gimp)

Add those to rules by default

Weird configurations

Multi-monitor

Crashes

Better release process (i.e. don’t just pack up git, TEST)

Testcases

Client on all desktops

There, back, there again

Client on last desktop

was interpreted as being on all desktops

Layouts

Refactor layouts to share more code

See vain This uses a simple “arrange” function as the layout function

More/better layouts

Implement BladeLayout as HalfLayout with masterCount == tiles.length

Multi-master in spirallayout

Crazy stuff

Layout switcher

Indicate layout/state (tiling on/off) somehow

Per-activity settings

Huge complexity increase (one additional layer on top of desktops/screens) Investigate how the actual relationship between activities and desktops/clients is Seems to be the following: Each client belongs to multiple activities, but is on the same desktop on each There can only be one activity at the same time

Needs changes in tilingmanager (large) and maybe tile and tilelist

React on configuration change

Right now kwin restarts are needed every time the configuration is changed

Report

Bugs

INPROGRESS Pixmap issue

Seems it corrupts when clients are resized before windowShown (when compositing) There are other cases, though, like firefox resizing after restoring the previous session https://bugs.kde.org/show_bug.cgi?id=341195

KWin maximizes windows automatically on certain conditions

Possibly caused by electricBorderMaximize

QML doesn’t draw stuff

options.useCompositing/compositingMode doesn’t keep up

It does not change to false when disabling compositing

Crash when wrong desktop is used in workspace.clientArea()

See #22

Stacking order is buggy

i.e. sometimes maximizing a client maximizes it below other clients or glow is below other clients

QTimer is not exported to qml

Either this or import functionality to javascript are needed to properly do resizes

Documentation

ClientArea options

conditions/guarantees (e.g. is windowClosed always executed before FFM selects new activeClient?)

Difference between geometryChanged and geometryShapeChanged

geometryChanged fires on geometryShapeChanged and a few other signals

windowClosed is only fired when compositing

Wishes

Integration with rules

Some way to draw small window borders

Outline doesn’t work as it darkens the window and consumes mouse input Effect?

Files

commentary.org

Latest commit

History