[Kde-games-devel] does this solve the multiple resizing bug foryou?

[Aaron J. Seigo]

On Wednesday 06 May 2009, Wolfgang Rohdewald wrote:
> On Donnerstag, 7. Mai 2009, Aaron J. Seigo wrote:
> > QRect r = desktop->availableGeometry(desktop->screen(window));
>
> so I took the default screen and you say I should take the actual screen
> the window is on. I will fix that.
> is there a difference between your code and availableGeometry(window)?
> I cannot see any. Documentation says: "returns ... of the screen which
> contains widget"

i always forget about that overload. maybe i just like typing? ;)

> > as for the geometry of the window including the window decorations you
> > can use KWindowInfo::frameGeometry; note however, that if your window is
> > maximized that it's likely to be == to the widget geometry.
>
> but a maximized window still has borders, so frameGeometry() should differ
> from geometry(). It actually does if I test it here. Did you mean
> fullscreen? That would be something I did not yet touch at all but will
> eventually have to for netbooks.

sorry, yes, fullscreen.

> Of course I would also prefer a fix directly in K/QMainWondiw. If I start
> kmj with the most complicated tiles and background and maximized and much
> more visible tiles than I normally show, this makes a difference of 12
> against 23 seconds: One resizing against three of them. So for me this is
> not just academical.

any time lost is bad; i don't think this is academic for any app, it's just a 
lot more noticeable for graphically complex applications.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-games-devel/attachments/20090506/c7f410ec/attachment.sig