Classes tab

[Milian Wolff]

On Wednesday 28 July 2010 14:46:36 Alvin Beach wrote:
> Hello,
> 
> I have recently switched from KDevelop 3.5.5 to KDevelop 4.0.1(using
> KDevPlatform 1.0.1) and am experiencing an issue with opening files in
> a Custom Makefile project.
> 
> When I double-click on a class (in the Classes tab), the installed
> version of the file (found in /usr/include) is opened rather than the
> file local to the project. I only noticed this when I attempted to
> save my changes and could not. From what I can tell, KDevelop4 is not
> first checking if the file to be opened is located in the current
> project directory. Instead, it seems to check the
> system /usr/include first.
> 
> Is this specific to a Custom Makefile Project? I have scoured the
> configuration of KDevelop4 and the Project's configuration and cannot
> see where I can change this behaviour. Am I missing something?
> 
> My system:
> openSUSE 11.3 (recently upgraded and decided to migrate my KDev3
> project to KDev4).
> KDE 4.4.4 release 2
> KDevelop 4.0.1(using KDevPlatform 1.0.1)

Yeah that happens from time to time and is really annoying. I think we should 
try to improve the situation by preferring files in opened projects when 
looking for imports in Cpp. I haven't looked at the code but it can fix 
multiple cases:

1) jump to declaration/definition
2) create class with inheritance (remember those <../../../usr/include/bla.h> 
includes?)
3) ...more?

I have sadly no time for that right now. Please report it on bugs.kde.org.

Thanks
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100728/7c321036/attachment.sig>