[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 162375] less agressive switch interface/implementation
From:       Jens Dagerbo <jens.dagerbo () swipnet ! se>
Date:       2008-05-21 21:05:44
Message-ID: 20080521210544.30938.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=162375         




------- Additional Comments From jens.dagerbo swipnet se  2008-05-21 23:05 -------
Right. I tend to focus on worst case scenario, and the problem I see is that I will \
find myself placed in potentially unfamiliar code, not knowing it is infact the body \
of the function I sought. 

Andreas, I agree that is useful. In fact, I think I would prefer to have it too. But \
this doesn't change that the result can be unexpected, which is never a good thinkg. \
Anyway.. I think you are right, it might be more good than bad.

> Then -- press ctrl+win+up (*) and voila you are at the beginning. 
> (*) let's ignore the fact that this feature is missing,  but it is 
> useful anyway to have it, so it will happen sooner or later :-) 

It isn't missing in KDevelop3. (I know, I implemented it.) The actions are called \
"jump to next/previous function" and have default shortcuts Ctrl+Alt+PgUp/PgDown. :)

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


[prev in list] [next in list] [prev in thread] [next in thread]