Re: Memory usage..

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Memory usage..
by koos on Thursday 27/Mar/2008, @13:38

Sounds like a great idea, since lots of windows are there as a container for other widgets. In my little extra gear project, the main window is completely covered with dock windows.
However with qt4.4 coming soon, there is only one native window and thus one double buffer. Just tried it with trunk and indeed the app looks completely broken with setAttribute(Qt::WA_PaintOnScreen);, docks aren't updated properly neither is the menubar and statusbar.

Related Links

·   Articles on Interviews
·   Also by koos
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Memory usage..
by Leo S on Thursday 27/Mar/2008, @13:57

>> However with qt4.4 coming soon, there is only one native window and thus one double buffer.

Are you sure? I think each widget still has its own double buffer. The native window issue is separate.

[ Reply To This | View ]

Re: Memory usage..
by Anon on Thursday 27/Mar/2008, @14:11

Your analysis is correct.

[ Reply To This | View ]

Re: Memory usage..
by koos on Thursday 27/Mar/2008, @14:38

No, just a guess actually. Hmm, I need to figure out why the app is so broken then, maybe paint events aren't passed to child widgets ...

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I'm adding spaces everywhere so that Charles doesn't edit the files." -- Stephan Kulow
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.