25 Jan
2013
25 Jan
'13
5:25 p.m.
Hi Timothy
Interesting! Martin, do you know if these bugs are still present in kwin?
For what it's worth, twin will not be replaced in the R14.0 cycle, but
kwin should be available as an unsupported option for R14.0 so that we
have time to find and fix problems such as the one you described above.
Also, I use multiple monitors on a daily basis, and have a older triple
head setup specifically for testing unusual configurations, so this issue
would have shown itself very quickly once kwin testing progressed to that
point. ;-)
Tim
The only items that I am aware of that might fit
this list of criteria
are
kwin, a handful of kcontrol modules, and possibly some smaller KDE
applications such as Okular. kwin is my current focus, and so far seems
to work very well without increasing the memory or CPU footprint. kwin
also satisfies Point #2 above by presenting a much smoother action in
high
resolution TDE sessions when compared with twin due to its integrated
compositing engine.
But kwin has much trouble with multi screen systems. It can't scale images
across two or more monitors and has a bugs in calculating the window size
-
i.e. minimize and maximize a windows shows holes in the window borders.
Hope, that multi screen will be tested exentsive than the bugs in KDE4 in
this
area stops me using it.
Fine regards
Rolf