On Tue, 16 Dec 2003 21:51:47 +0100 (CET) Martin Jost <[EMAIL PROTECTED]> wrote:
> Could the threading/sorting-interaction please be changed in the following > way: Threading is done first, in the "usual" way. Sorting comes as a second > step. Sorting regards the whole threat as one entity. While this could make sense for dates, I don't think it would be really helpful if sorting by sender or any other criterion. On the other hand, whenever I have to sort on any other criterion than date, I also disable threading. So maybe this would not be so much of a problem. The implementation of such a feature would probably not be too difficult. One just needs to traverse the tree and note, for each message, the 'sorting value' to be used: it is the smallest of those of the lower-level messages. Then apply the existing sorting algorithm on those 'sorting values' instead of the original values. But there is something else... Considering the newest message to tag the entire thread means that any incoming message may move a whole thread. Not very nice if it happens when you're looking at this thread or another nearby... While the current method ensures that an incoming message will not require that any other messages are moved: the new one is just inserted at the correct place. -- Xavier Nodet "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.
pgp00000.pgp
Description: PGP signature
