From kde-core-devel  Sun Dec 03 20:43:17 2006
From: Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date: Sun, 03 Dec 2006 20:43:17 +0000
To: kde-core-devel
Subject: Re: RFC: Making focus information visible for panes
Message-Id: <200612032143.19360 () erwin ! ingo-kloecker ! de>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=116517877425381
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2206502.xiEhZGvKo4"

--nextPart2206502.xiEhZGvKo4
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 30 November 2006 21:42, Joseph M. Gaffney wrote:
> On Thursday 30 November 2006 15:03, Ingo Kl=F6cker wrote:
> >  The downside of this is that one can't use the up/down arrow
> > keys for navigating in the message list pane because up/down
> > scrolls the message in the preview pane.
>
> Something I, as a user, find fairly annoying actually.  Even in KDE I
> use my keyboard shortcuts, and this is on thing I miss greatly from
> other mail clients.  Now perhaps I'm missing something - why is it
> intentional that no KMail pane ever has focus?

Because this way the user never needs to remember or check which pane=20
has focus. He can simply press left/right to go to the previous/next=20
message and simply press up/down to scroll the message without having=20
to think about the focus. If the keyboard focus doesn't get in his way=20
then he can much better focus on what he actually wants to do.

The alternative is that you press up/down because you want scroll the=20
message but unfortunately the folder list has focus so that you=20
inadvertently switch to another folder. In order to prevent this (to a=20
certain degree) some way to clearly indicate which pane has focus is=20
needed (which is what this thread is about).

Regards,
Ingo

--nextPart2206502.xiEhZGvKo4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBFczbnGnR+RTDgudgRAh4KAJ9P2lnQxWmQ5ocJeY65jyI1XR24aQCeLtK7
XYnnQsI4D3/BEkVTg0w74eI=
=m5bc
-----END PGP SIGNATURE-----

--nextPart2206502.xiEhZGvKo4--