[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    readDockConfig
From:       falk.brettschneider () gmx ! de
Date:       2003-05-28 5:59:11
[Download RAW message or body]

Hi Robe,

I saw in the code you show() the mainwindow too early.
If you call MainWindow::show() earlier than
KDockMainWindow::readDockConfig(), then internally a huge number of QWidget::reparent() calls and related
events are queued and executed during the visible startup (under heavy CPU load
so to speak). That lets several event-timing problems of Qt and some
race-conditions occur. That's why the re-docking seems to be failed and looks so
"buggy". The only thing we can do is to avoid showing the mainwindow as long as
the widgets-docking (initial creation of all widgets _and_ after that the
execution of readDockConfig() for re-docking) isn't finished. To improve the
startup responsibility, KDevelop rather should move its project loading to after
the MainWindow::show() execution.
There must be 2 stages of startup. First try to build up the widgets as fast
as possible to be visible, second load the recent project and stuff.

Ciao
F@lk

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!


_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]