https://bugs.kde.org/show_bug.cgi?id=205494

           Summary: modifying a headerfile and ctrl+tab sometimes refuses
                    to switch tab
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs@kdevelop.org
        ReportedBy: spectral@mindkiller.com


Version:           svn r1015724 (using KDE 4.3.0)
Compiler:          gcc 4.4.1 
OS:                Linux
Installed from:    Unlisted Binary Package

When I have (among other things) a header file and the .cpp implementation file
open in 2 tabs and I modify the header file it triggers a "rescan" of the .cpp
file - this is fine, except if you aren't fast enough to ctrl+tab back to the
.cpp file it won't switch to that tab. It will simply stay in the header file
tab.

It's tricky to describe.. So I'll try to give some more in-detail description.
1) open foo.h and foo.cpp
2) go to foo.h tab and change something - add a class member or a function
definition for example.
3) now it will trigger a rescan of the headerfile (blue progress bar in the
status bar). I'm unsure if it is just rescanning the header file or if it also
scans any other files that include this header file as well (i think so?) or if
it just reparses the .cpp file when i switch to it.
4) this is the tricky part - how to consistently reproduce it. but on my rather
slow CPU (athlon xp 2400+) if i wait for about half a second after i made my
last change and press ctrl+tab just once to get back to the .cpp file (if that
was where i was prior to switching to the header file tab) - it won't switch to
the .cpp file. It will display the list of open tabs but I'm still in the
header file tab. If I switch fast enough or slow enough, it will however send
me to the .cpp tab.

background parser delay is set to 500ms and 1 thread.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs