Bug 149310 - Ctrl+Home does not select first entry
Summary: Ctrl+Home does not select first entry
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: message list (show other bugs)
Version: 1.9.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-28 21:42 UTC by Maciej Pilichowski
Modified: 2015-04-12 10:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2007-08-28 21:42:19 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs

Ctrl+home works as go to the top (begin) of the mail list.

Well, press it :-) There is movement, but you will see only dotted rectangle, item will be not highlighted.
Comment 1 Thomas McGuire 2007-08-30 18:47:40 UTC
Confirmed. Although the current item is set to the first item, the selected item is still the old one.
Comment 2 Martin Koller 2009-08-21 23:06:24 UTC
It seems this is the default behavior of the QTreeView. Home and End (without CTRL) move to first/last message including selection.
Don't know why this is, but I'm not sure if we should change that, as all other tree widgets would have a different behavior then.
Comment 3 Maciej Pilichowski 2009-08-22 08:07:42 UTC
Martin, and when there is no selection?

But I am not pointing out where the active element went, but the issue it is not highlighted so the user does not know what message is active one (by looking on the list).
Comment 4 Bernd Oliver Sünderhauf 2012-08-24 12:23:04 UTC
Wont'fix, as this is no bug but a very practical design decision allowing to mark multiple lines separately.
Comment 5 Laurent Montel 2015-04-12 10:13:21 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.