You’re Going the Wrong Way!

In Opera's built-in mail client "M2", if you sort a message list by date in descending order, new messages (by date) will be up top.

Then, if you enable "view -> threaded", messages will be grouped into threads and newer threads (by date) will be up top. And, updates to a thread will cause that thread to jump up to the top of the list (with no way to turn that off btw).

This is all great, but there's a *huge* problem. The messages in a thread are sorted by date in descending order too.

For example, you'll get this:


- Thread Starter
- reply 5
reply c
reply b
reply a
reply 4
- reply 3
reply b
reply a
reply 2
reply 1

instead of this:


- Thread Starter
reply 1
reply 2
- reply 3
reply a
reply b
reply 4
- reply 5
reply a
reply b
reply c

This makes sorting by date in descending order while using threading absolutely horrible. It's so horrible that I've switched to sorting by date in ascending order just so messages in the thread are ordered correctly. The downside of this is everything new is at the bottom of the list. But, there's no alternative.

You're going the wrong way!

7 Replies to “You’re Going the Wrong Way!”

  1. Several people are complaining about this now, they really don’t want it. They want to open a large thread and expect the newest unread stuff to be at one click away. They are typically mouse users, and don’t use ‘g’. How can we please everybody?

  2. Originally posted by alexremen:Several people are complaining about this now,:(Originally posted by alexremen:How can we please everybody?Not sure how many places in the code you had to change to make this work and how long each part is. But, if it’s not much to have both code paths, an option would be nice. Or, refactor the loop where an option decides whether the start message is the first or last node and then whether to increment or decrement. That way the code would stay cleaner.Or, revert it if it’s that much of a problem. I’ll just use sort in ascending order and do everything at the bottom of the list. Then, maybe something cool could be invented later on.Or, revert it and implement it via #2 in DSK-252234? Or, have an option and do #2 as another option. (Users have expressed a desire to turn off #1 via an option btw)

  3. Originally posted by alexremen:Several people are complaining about this now, they really don’t want it. They want to open a large thread and expect the newest unread stuff to be at one click away. They are typically mouse users, and don’t use ‘g’. How can we please everybody?How about offering a setting to do it either way?

Leave a Reply

Your email address will not be published. Required fields are marked *