Plasma and TwinView [Was Re: Release schedule clarifications]

[Andreas Pakulat]

On 25.10.07 13:42:58, Aaron J. Seigo wrote:
> On Thursday 25 October 2007, Andreas Pakulat wrote:
> > On 25.10.07 21:20:55, Andras Mantia wrote:
> > Thats pretty similar to what you get when you setup Xorg with 2 screens
> >
> > and disable Xinerama, 2 independant desktops. Which I think explains:
> > >  With KDE4, I didn't check what was on the second screen as I usually
> > > don't have the TV turned on when I work, or if it is, my wife is
> > > watching it (like now). :) But on the main screen nothing was unusual,
> > > the panel had the right size, the toolbox in the top-right corner
> > > appeared correctly,
> >
> > Why you didn't see a too-large-panel or the wrong Toolbox, this stuff
> > apparently only happens with Xinerama setups.
> 
> which probably tells us exactly where the issue is... here's how that code 
> works:
> 
> Corona::loadDefaultSetup creates a DesktopContainment (which is in 
> workspace/plasma/containments/desktop/) for each screen. the containments are 
> set to the size of the screen and set next to each other on the canvas.
> 
> plasma (the actual binary, in workspace/plasma/plasma) then sets up a 
> QGraphicsView per screen, full screens and desktop-izes it and sets the 
> sceneRect() to be the DesktopContainment for that screen.

I understood how it works, but I guess I'd need to read the code to
understand where exactly the error lies - right? (because from your
description its not that obvious) :)

> oooh. i just realized one source of additional and unnecessary slow down on 
> xinerama systems: the DesktopContainments are too close and the AA is causing 
> pixel bleed. i fixed this the other day for the panel with a margin. damn. 
> let me do the same fix for the DesktopContainments. =))

Aaron, you really rock!

Andreas

-- 
Good news from afar can bring you a welcome visitor.