Bug 72832 - The classes tree is closed after running the project
Summary: The classes tree is closed after running the project
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: classbrowser (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
: 116389 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-01-17 17:32 UTC by András Manţia
Modified: 2013-03-31 01:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description András Manţia 2004-01-17 17:32:41 UTC
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.
Comment 1 Tapio Mattila 2004-02-12 10:46:45 UTC
KDE version 3.0.0 buildt from sources (konstruct)

Same behavior also when doing compile and build, class view always closes.
Comment 2 Jeroen Wijnhout 2004-02-12 10:54:02 UTC
Same here (latest KDE_3_2_BRANCH), quite annoying indeed. Too bad, for such a wonderful app.

best,
Jeroen
Comment 3 András Manţia 2004-02-12 11:07:26 UTC
I'm particulary sad because it worked before (prior to the Nove Hrady 
meeting). 

Comment 4 Simon Berger 2004-03-09 15:49:45 UTC
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? 
Comment 5 Steven T. Hatton 2004-03-09 20:33:08 UTC
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.
Comment 6 András Manţia 2004-03-09 20:39:50 UTC
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-----

Comment 7 Simon Berger 2004-03-10 00:04:59 UTC
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.
Comment 8 Jens Dagerbo 2005-11-16 10:27:55 UTC
*** Bug 116389 has been marked as a duplicate of this bug. ***
Comment 9 Jens Dagerbo 2006-04-27 00:50:27 UTC
Fix in SVN commit 534353 on 3.4 branch.
Comment 10 Aleix Pol 2013-03-31 01:31:58 UTC
moving to kdevplatform's classbrowser