Various bugs/tweaks

Tarjei Knapstad tarjeik at
Thu Feb 21 20:21:47 GMT 2002

On Thu, 21 Feb 2002, Roland Krause wrote:


> Tarjei,
> my guess is that you have no tag file support. If you do then this
> should not happen but you should be presented with a choice of files. 
> Otherwise it is a bug, let me know about it and I will fix it so that
> you can either choose or we setup some automagic. 
That is correct. After switching on tags, I get a dialog with choices.  
This is quite cumbersome however. Actually, pressing F12, getting a list
of choices, grabbing my mouse and double clicking the correct file, is at
least the same work as just grabbing the mouse and selecting the correct
file from the fileview. After all, the point of F12 should be a keyboard
_shortcut_, not a complicated procedure, to jump between
header/implementation files.

So I still vote for some automagic here. If one edits a file called 
MyDialog.cpp in a directory, and then presses F12 to jump to MyDialog.h, 
who would expect it to jump to MyDialog.h in a completely different 

I don't know about others, but I allways keep the implementation of my
headers in the same directory. If other people have different habbits, 
maybe this calls for a vote - or better - a configuration option.

What do you say?

> --- Tarjei Knapstad <tarjeik at> wrote:
> > Well, only one bug actually :)
> > 
> > I have several libraries in my project which reside in different 
> > namespaces. A few of these have classes with the same name, and thus
> > the 
> > same filename due to standard naming conventions. If I try to press
> > F12 
> > to switch between the header/implementation I end up with the wrong 
> > .cpp/.h file. My guess is that all filenames are sorted
> > alphabetically in 
> > a list and the first matching .cpp/.h file is the one switched to.
> > 
> > Example:
> > a/Test.h
> > a/Test.cpp
> > b/Test.h
> > b/Test.cpp
> > 
> > If I'm editing b/Test.h and press F12 I'm sent to a/Test.cpp. In
> > other 
> > words, lookup should also check path when F12 is pressed.
> > 
> > Next some minor tweaks regarding tab page modes:
> > 1. Coloring the tabs will be a good help when you're looking for a
> > file.
> > For instance, color the Documentation tab green, header files red,
> > and 
> > implementation files blue
> > 
> > 2. Allways make the documentation tab the leftmost tab. When you've
> > got a 
> > lot of files open it would be nice to be able to quickly access the 
> > documentation you're currently using, without trying to read
> > truncated 
> > tab names (the colors will help, but since there's only one doc tab,
> > why 
> > not insert it at a constant position so the user won't have to look
> > for 
> > it at all?).
> > 
> > Regards,
> > -- 
> > Tarjei Knapstad
> > 

Tarjei Knapstad

to unsubscribe from this list send an email to kdevelop-request at with the following body:
unsubscribe »your-email-address«

More information about the KDevelop mailing list