Bug 291528

Summary: Make "In file included from" output clickable
Product: [Developer tools] kdevplatform Reporter: David <daviddoria>
Component: outputviewAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: wishlist CC: aleixpol, mvolden2
Priority: NOR Keywords: junior-jobs
Version: git master   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 5.0.0

Description David 2012-01-14 17:08:29 UTC
Version:           git master (using Devel) 
OS:                Linux

When there is a compiler error, it shows the stack of files which were included to get to the error. For example:

In file included from /media/portable/Projects/src/PatchBasedInpainting/PriorityFactory.h:52:0,
                 from /media/portable/Projects/src/PatchBasedInpainting/PatchBasedInpainting.hxx:29,
                 from /media/portable/Projects/src/PatchBasedInpainting/PatchBasedInpainting.h:182,
                 from /media/portable/Projects/src/PatchBasedInpainting/Tests/TestPatchBasedInpainting.cpp:19:
/media/portable/Projects/src/PatchBasedInpainting/PriorityFactory.hxx: In static member function ‘static Priority* PriorityFactory<TImage>::Create(PriorityFactory<TImage>::PriorityTypes, const TImage*, const Mask*, unsigned int)’:
/media/portable/Projects/src/PatchBasedInpainting/PriorityFactory.hxx:81:56: error: type/value mismatch at argument 2 in template parameter list for ‘template<class TImage, template<class> class TPriority> class PriorityManual’

It would be great if you could click on those lines and have it take you to the #include in the file. It already knows the file and line number, so it should be pretty easy :)

Reproducible: Always

Steps to Reproduce:
Produce a compiler error and look at the "included from" output.

Actual Results:  
You can't click on the "included from" lines.

Expected Results:  
You can click on the "included from" lines.
Comment 1 Kevin Funk 2012-12-21 00:07:50 UTC
Still not possible. CCing someone who worked on this.
Comment 2 Kevin Funk 2017-01-12 15:05:12 UTC
That works since quite some time now. Marking as resolved.

Not sure when it got fixed, assuming the 5.0 release has it.