Re: Balsa's thread handling very buggy.
- From: Miquel van Smoorenburg <miquels cistron nl>
- To: Peter Bloomfield <PeterBloomfield bellsouth net>
- Cc: balsa-list gnome org
- Subject: Re: Balsa's thread handling very buggy.
- Date: Tue, 15 Jul 2003 11:13:28 +0200
On 2003.07.14 18:20, Peter Bloomfield wrote:
> On 07/14/2003, Andrew Lau wrote:
> That's by design. The handling of threads was discussed on the Balsa
> list a couple of years ago (see in particular
> http://mail.gnome.org/archives/balsa-list/2001-October/msg00552.html )
> and the consensus was that a message operation is always a message
> operation, not a thread operation, regardless of whether the thread is
> expanded or collapsed.
What is irritating is that if your mailbox is set up to open with all
threads expanded, and you delete a message at the top of the tree,
the rest of the tree is collapsed.
Worse, the thread usually spreads into several subthreads because the
parent is gone.. all collapsed.
Which means if you have a mailbox with a huge thread in it (say 60 messages)
it becomes very hard to delete that thread .. delete a few messages, the
thread changes into several sub-threads, scattered throughout the
mailbox, all collapsed, you need to expand them all, start deleting,
which results in several collapsed subthreads ... argh!
IMO there are two bugs here:
1. When the parent is deleted, the thread should still be linked together.
I'm using JWZ threading, I read the algorithm description, and it
should be no problem. Just a UI bug ?
2. Deleting a message in a thread should not result in the rest of the
thread getting collapsed
Mike.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]