After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616724 - Initialize message window with threaded state of main window
Initialize message window with threaded state of main window
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[kill-bonobo]
: 620936 621513 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-04-24 18:25 UTC by B S Srinidhi
Modified: 2010-06-22 18:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description B S Srinidhi 2010-04-24 18:25:46 UTC
Steps to reproduce:

When msg list is sorted;

1. Sort the message list according to "Received" time in "Descending order"
2. Open a mail in a new window / preview window
3. Press "Ctrl+PgDn" to read the older message (mail below the current selected mail), but the "newer" message is opened.
(Similar behavior for the "Ctrl+PgUp)

When msg list is threaded:

1. Group the message list by threads
2. Open a mail in a new window / preview window
3. Press "Ctrl+PgDn" to read the older message (mail below the current selected mail, as part of the current thread), but instead the "newer" received message is opened
(Similar behavior for the "Ctrl+PgUp)

The same happens with the "." keyboard shortcut to read the "next" mail in the message list.

Evolution 2.30.0.1
Comment 1 Andrew Ruthven 2010-06-02 00:51:31 UTC
What appears to me to be happening is when you select to go to the next message when in threaded mode is that it is in fact selecting what would be the next message in the default order.

So the threaded mode isn't being applied to the message window.

Rather annoying...
Comment 2 Andrew Ruthven 2010-06-17 21:53:38 UTC
It seems that using a message window the list of messages in the main window is totally ignored.  If you have a filter, open a message in a message window, when you step through the messages it totally ignores the filter.
Comment 3 Matthew Barnes 2010-06-17 23:04:03 UTC
That's because each message window has its own message list that it's navigating over -- separate from the one in the main window.  Need to look into how best to fix this.
Comment 4 Matthew Barnes 2010-06-19 15:44:33 UTC
Fixed in:
http://git.gnome.org/browse/evolution/commit/?id=0439c01a9ab20875796c8ecae855627424742bf4

Note that message windows inherit the main window's threaded mode when the message window is created, but does not track the main window's threaded mode thereafter.
Comment 5 Matthew Barnes 2010-06-20 21:40:32 UTC
*** Bug 621513 has been marked as a duplicate of this bug. ***
Comment 6 Matthew Barnes 2010-06-20 21:41:46 UTC
*** Bug 620936 has been marked as a duplicate of this bug. ***
Comment 7 Giacomo Perale 2010-06-20 22:05:31 UTC
Hi, I didn't apply the patch yet so ignore this message if this is solved, but here and in the patch you mentioned only inheriting the threaded mode. It seems to me that this is not the real bug, the message list used by the message window should inherit all of the properties it has in the main window (as it used to be with evolution <2.30)

For example now if you order the messages by date with the most recent message on top the Next/Previous buttons in the main window go respectively to the newer/older message, but in the separated window they go respectively to the older/newer message. The same happens when you order the messages by author, or subject: they still go to the older/newer by date.

Is this fixed by the patch you committed?
Comment 8 Giacomo Perale 2010-06-22 18:14:25 UTC
Since my issue is slightly different I created a new bug report, bug 622423.