Improvement regarding tabs overflow

[David Nolden]

The switch header/source feature already exists since always, and duchain
navigation (previous/next context) is completely independent of the open
tabs.

You should take an exact look at the "Navigation" menu before asking for new
navigation-features. ;-)

Regarding bookmarks you're right, we're missing a session-wide bookmarking
system at the moment.

Greetings, David

Am 12.12.2010 22:58 schrieb "Konstantin Karganov" <karganov at gmail.com>:

For me the most annoying tab management feature (and its REALLY
annoying!) is losing the context when closing the tab.

In KDevelop DUChain navigation works really nice, so I use it
intensively when browsing the code.
And most typical use case is reading file1 -> clicking on some
usage/declaration position -> going to file2 -> navigating to some
usage -> going to file3 etc, and the chain of open files may be quite
long.
If by chance I open wrong usage position or any file I don't need and
close it, then - OPS! - I don't get to previously opened position but
to some random tab instead. (Yes, I understand that it may be just
next or previous file in tab group, but in the context of browsing the
code it's completely random, I lose the whole browsing history).

In MSVS I used to set bookmarks for important code places, they
persist if the solution is closed, but in KDevelop there are no decent
bookmarks navigation...

Plus, I'd heavily agree with Syron, opening .h near .cpp and vice
versa would be very nice. Lack of such feature was very annoying in
MSVS and it is in KDevelop either. In C and C++ *.h and *.cpp files
are actually one semantic entity, they should be together since both
are opened. And, I guess it's easy to implement, just open new tab in
proper position.

More, I disagree with keeping current tab in the center, from
usability point of view it looks as awful as dynamic changing menu
commands order or hiding less recently used commands. For example, you
know that your main .cpp file is on the right in tab list, then you
switch to some header opened, then to another header and your previous
file tab is still in the same position, reachable in one click.
If you make the tabs scroll automatically it will confuse much more than
help.


On Mon, Dec 6, 2010 at 10:55 PM, Sven Brauch <svenbrauch at googlemail.com>
wrote:
> Hey,
>
> I also t...
--
Best regards,
Konstantin.

--

KDevelop-devel mailing list
KDevelop-devel at kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/lis...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101213/a93eb370/attachment.html>