From 932f96d8b610c8e2a3de25ef2e028b5f0dfb9d56 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lubo=C5=A1=20Lu=C5=88=C3=A1k?= Date: Sat, 4 Nov 2006 07:29:20 +0000 Subject: [PATCH] Ideas for debugging effects. svn path=/branches/work/kwin_composite/; revision=601722 --- COMPOSITE_TODO | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/COMPOSITE_TODO b/COMPOSITE_TODO index 8c7ae3100f..4f81d1ff0a 100644 --- a/COMPOSITE_TODO +++ b/COMPOSITE_TODO @@ -223,4 +223,18 @@ Effects TODO + - needs support for new window types from the current draft of the EWMH WM spec + - needs patching Qt, netwm* classes in kdecore ++ showftp effect + - for debugging, just shows transparent fps in some corner + - just painting the number in paintScreen() should do, with glPushMatrix() and glLoadIdentity() + to avoid all transformations ++ - needs bindPixmapToTexture() or something like that, for displaying the text + - should also detect kwin being idle - it probably should detect in pre-paint that the only + damage is its own area and avoid damaging for the next round in post-paint + ++ debugpaint effect + - should show what is damaged during each repaint step + - probably just e.g. paint a red almost transparent area over damaged areas + - needs special care to avoid causing infinite loops by its own damage (i.e. it damages + part of screen to clear its own painting, that triggers itself again next repaint) + ? other effects