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

List:       kde-bugs-dist
Subject:    [Bug 162375] less agressive switch interface/implementation
From:       Maciej Pilichowski <bluedzins () wp ! pl>
Date:       2008-05-21 20:31:50
Message-ID: 20080521203150.12955.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=162375         




------- Additional Comments From bluedzins wp pl  2008-05-21 22:31 -------
If I might...

Jens, let's focus on most disastrous scenario -- you are running Kdevelop for 8 days, \
you switched to implementation and you are in the middle of some horrible 4000-lines \
function. 

Fact -- you are inside implementation -- that's a guarantee (by KDevelop, because \
switch was made).

Now -- I cannot see why header function (which I already saw, it is a interface after \
all) is better than function. But let assume your point of view that it is better to \
start from, well, the start.

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 :-)

So... I agree that "focus follows mind" is great :-) but I see nothing wrong with the \
behaviour I described above. a) no surprises
b) ability to mimic current behaviour
c) advantage of smart switch -- almost focus follows mind, when it is correct, you \
are not distracted at all, the work is fluent, if it is not right, there is no \
saving, but there is no loss either

Summing up -- in some cases there is no difference, in some there is advantage.


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