Bug 28505 - After closing configuration dialog next new message is selected
Summary: After closing configuration dialog next new message is selected
Status: CLOSED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-08 23:03 UTC by Ingo Kl
Modified: 2010-04-02 12:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Kl 2001-07-08 22:26:00 UTC
(*** This bug was imported into bugs.kde.org ***)

Package: kmail
Version: current cvs
Severity: normal
Installed from:compiled sources
Compiler:gcc 2.95.2 19991024 (release)
OS:Linux (i686) release 2.4.2-4GB (SuSE)

I encountered the following strange bug (?). To reproduce do the 
following:
1. Go to a folder which contains new messages (which are marked in red).
2. Open the configuration dialog.
3. Either press Close or Apply.
Observation: The next unread message (from the top of the header list) 
is selected. Also if you already read some messages in this folder and 
there were open threads which after reading did't contain anymore any 
unread/new messages they are closed after closing the configuration 
dialog.

I guess this strange behaviour occurs because the folder is reopen 
after applying/closing the configuration dialog. I don't think this is 
intended. Or is it? After changing the threading options this might be 
necessary (or maybe not). But if the user only changed for example the 
font this shouldn't happen.

BTW I don't like the behaviour that automatically the first new 
message is selected if you go to a folder which contains new messages. 
IMHO it would be better to simply go to the last message the user read 
in this folder as it is done if the folder doesn't contain any new 
messages.

Regards
Ingo
Comment 1 Michael Haeckel 2001-08-15 12:11:03 UTC
fixed
Comment 2 Björn Ruberg 2010-04-02 12:38:23 UTC
*** Bug 232629 has been marked as a duplicate of this bug. ***