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

            Bug ID: 361958
           Summary: outline dropdown widget jumps to function
                    implementation in another file
           Product: kdevelop
           Version: git master
          Platform: Compiled Sources
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: CTags
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: rjvber...@gmail.com

The file outline navigation widget does not function reliably. Even if it shows
all functions provided in a (C++) source file, using it to jump to a function
implementation may in fact open the implementation in a different document.

This is very counterproductive as most of the time one doesn't notice the
change in open document, esp. if the document was already open (for reference).

Reproducible: Always

Steps to Reproduce:
1. open a project that provides different implementations of a given class,
e.g. for different supported platforms as is relatively common in the KF5
frameworks source.
2. open the source file for one of the implementations
3. use the outline navigator to jump to a given function implementation

Example the KDE4libs sources (sorry...) which provide platform specific
implementations in kdeui/kernel/util/kwallet.cpp and
kdeui/kernel/util/kwallet_mac.cpp .

Actual Results:  
In the above example, using the outline to jump to an implementation in
kwallet_mac.cpp opens the implementation from kwallet.cpp instead.

Expected Results:  
A document-specific outline navigator does not jump to a different file unless
this is explicitly clear, like when jumping to a declaration in a header file.

Developing/expanding the outline entry does show that the reference in fact
points to a different file, but most of the time one will execute the jump by a
double-click on the entry.

The expected result seems self-evident, but in a more general context, the
ctags feature sh/could use data from the project importer to exclude files that
will not be built (and it wouldn't hurt to distinguish files based on that
criterium in the project view).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to