Bug 54488 - Kdevelop puts the wrong includes when automatically creating subclasses
Summary: Kdevelop puts the wrong includes when automatically creating subclasses
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-11 17:19 UTC by Barry Stokes
Modified: 2003-05-10 04:00 UTC (History)
0 users

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 Barry Stokes 2003-02-11 17:19:47 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          GCC 3.2.1 
OS:          Linux

(This is using KDevelop 3 alpha 3 (gideon) on KDE3.1 on a RH8 system, compiled from sources with GCC 3.2.1)

When using KDevelop to create a new class (Project->New Class), and you tell it to use a base class. If that base class has any capital letters in it, the Kdevelop will ignore this when putting the #include statement into the newly generated .h file. It just puts everything in in lower case. This then means that you have to go and modify each .h file that is produced this way.

For an example:
if I have a class GLWindow, and I tell KDevelop to create a new class with that as the base class, it puts #include "glwindow.h" instead of #include "GLWindow.h".
Comment 1 Caleb Tennis 2003-02-11 20:44:48 UTC
Argh - I fixed this very thing a few months ago.  Looks like somebody broke it... 
You used to be able to assign whether it generates filenames that are all lowercase or match 
the case of the classname. 
Comment 2 Jens Dagerbo 2003-05-10 04:00:34 UTC
Seems fixed in CVS.  
 
When you state the base class, the dialog suggests where this class is defined 
and if that filename is incorrect it's just a matter of correcting it before pressing 
OK on the dialog.