--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Markers for range selections not updated as necessary
- From: Ulrich Eckhardt <doomster@knuut.de>
- Date: Sun, 20 Dec 2009 10:26:34 +0100
- Message-id: <200912201026.34572.doomster@knuut.de>
package: kmail
version: 4:4.3.2-1
severity: critical
After several operations on a folder the marker for the currently selected
message is not updated correctly. It seems that there are actually two
markers, one for the GUI, which is handled correctly, and one for internal
uses, which isn't. The latter one seems to be an index which isn't updated in
several cases.
Example:
* Select the first mail in a folder.
* Now change the sorting order.
* The previously selected message is still highlighted by the GUI, let's
assume that it now is at position 6 in the list of messages.
* Hold the shift key and click on the message at position 3 in the list.
At this point now, I would expect that messages at the position 3, 4, 5, 6 are
highlighted. Instead, messages at position 1, 2, 3 are highlighted, while the
highlight on position 6 is removed.
Similarly, when deleting mails the first following mail is highlighted by the
GUI while the internal index isn't.
Concerning the severity and why this is not just an annoyance, the reason is
that it is not always obvious what is going on when the start of the selection
range isn't visible. I was just cleaning up some old mails and there was one
from a source which I don't care for any more. I selected that, changed the
selection to "sort by author", scrolled down the list, shift-selected the last
of them and deleted them. Since the start of the selection remained close to
the beginning of the whole folder, far out of view, this just cost me a few
hundred mails.
Uli
--- End Message ---
--- Begin Message ---
Dear bug submitter,
Thank you for reporthing this issue. The bug has been determined not to be
Debian specific, and therefore was reported in the KDE bugtracker; see
https://bugs.kde.org/show_bug.cgi?id=219842.
We are sorry it has not been resolved. However, the version in which the
issue was reported is now obsolete and the upstream tracker has closed the
issue. Thus we are also closing the issue in Debian bug tracker.
If you think the bug is still relevant to a KDE Pim version in Debian stable
(aka Stretch) or newer -- i.e. part of KDE Applications 15.08.0 or newer --
then please open a new bugreport upstream and add your new information in the
upstream bugreport.
Again, thank you for reporting the issue. If there are any questions feel free
to ask.
KDE upstream bug tracker closed their bug with following statement:
"This bug has only been reported for versions before 15.08.0, which have been
unsupported for at least two years now. Can anyone tell if this bug still
present?
If noone confirms this bug for a Framework-based version of kontact
(version 5.0 or later, as part of KDE Applications 15.08 or later),
it gets closed in about three months.
Just as announced in my last comment, I close this bug.
If you encounter it again in a recent version (at least 5.0 aka 15.08),
please open a new one unless it already exists. Thank you for all your input."
--- End Message ---