Summary: | Splash screen makes machine unusable while Kdevelop is loading | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Nick Leverton <nick> |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | l.lunak |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nick Leverton
2004-05-04 18:23:00 UTC
Huh!? On my system (KDevelop CVS HEAD - on a P4/1800) the splash: 1. Is open about 4 seconds 2. Is minimizable 3. Is movable 4. Closes if you simply click it. On Tue, May 04, 2004 at 04:45:33PM -0000, Jens Dagerbo wrote: > > ------- Additional Comments From jens.dagerbo swipnet se 2004-05-04 18:45 ------- > Huh!? > > On my system (KDevelop CVS HEAD - on a P4/1800) the splash: > 1. Is open about 4 seconds Two minutes + for me, if none of it is in cache. (400Mb K6/2 500). I _know_ it's going to be slow to start up for those of us who make efficient use of old hardware (and can't afford upgrades). But it prevents me doing anything else whilst it's loading. > 2. Is minimizable Nope > 3. Is movable Nope > 4. Closes if you simply click it. Nope Maybe HEAD has been improved. Nick All of that should be in the 3.0.x releases, at least in 3.0.3. What version of KDevelop are you running? Please use KSplashScreen instead of your own widget for the splash (KDE3.2+). Yes, moving to KSplashScreen is on the TODO. It's trivial and could be done in a few minutes, but it never feels important enough to do it.. ;) Btw, Nick.. is it the documentation plugin that takes so long to load? It would seem likely, it was slow on any box. You'll be happy to hear it's been replaced, and the new plugin loads in a snap. :) The splash is now based on QSplashScreen and is now only on top of the loading KDevelop, not topmost on the desktop. FIXED. |