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

List:       kde-bugs-dist
Subject:    [Bug 141012] code completion is too slow
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-10-12 19:32:25
Message-ID: 20071012193225.9174.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=141012         




------- Additional Comments From apaku gmx de  2007-10-12 21:32 -------
As David Nolden already said on another bugreport its not a good idea to open very \
large projects in KDevelop3 because all files in the project are parsed and all the \
information stored in memory. 

This particular change makes sure that all the various plugins in KDevelop are \
properly notified when a file is re-parsed, i.e. its contents changed. I don't quite \
understand why that would slow down code-completion as this code-path is not executed \
during completion (it might be executed during editing, so if you use auto-completion \
you should turn the auto-completion off).

Anyway, this sounds like a "cantfix", at least of kdevelop3, its just not suited to \
be used on such large projects, it already has problems with "small" ones like \
kdelibs or Qt4. The situation should be better for KDevelop4 though.


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