KDE CVS from 2004/01/17. After the project is run, the whole tree in the Classes view is closed. Very annoying as you must reopen and select the class you are working on after every run. Bug present since the Nove Hrady meeting.
KDE version 3.0.0 buildt from sources (konstruct) Same behavior also when doing compile and build, class view always closes.
Same here (latest KDE_3_2_BRANCH), quite annoying indeed. Too bad, for such a wonderful app. best, Jeroen
I'm particulary sad because it worked before (prior to the Nove Hrady meeting).
It only happens when the build process finishes successfull. After compile errors the class view stays open. Might be somewhere near CppSupportPart::parseProject, maybe ClassViewPart::refresh called by signal updatedSourceInfo?
There are probably good technical reasons for this happening. I believe it may be related to my wishlist item. http://bugs.kde.org/show_bug.cgi?id=77042 The tree is probably rebuilt when the project is built. The tree isn't simply closed, it is regenerated. Trying to recover the state of the tree prior to building may be more challenging than it appears. Before I run off at the mouth any further, I'll wait to see what the codemeisters have to say on the issue.
I know that technically it can be regenerated and I know how hard is to restore the state of such a tree (I had the same problems in Quanta), but at that time when Quanta behaved in a similar mode I get lot of complaints and now I believe those reporters that it's very annoying. Maybe the most annoying thing in KDevelop. ;-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFATh1STQdfac6L/08RAlmwAJsFwrF8jQP3u+nxhib/AibgybyhtACgt09j XUN5MhzyfShX9GLpUjTdKws= =gIPN -----END PGP SIGNATURE-----
I have just removed the call of parseProject in CppSupportPart::slotProjectCompiled() (file languages/cpp/cppsupportpart.cpp, line 1114 in 3.0.1 release) and it seems to work. A possible negative effect of this hack is that files modified during the build process are not reparsed. I have no idea if there are other side effects (inconsistent class db ...), so use with care.
*** Bug 116389 has been marked as a duplicate of this bug. ***
Fix in SVN commit 534353 on 3.4 branch.
moving to kdevplatform's classbrowser