[haiku-commits] Re: haiku: hrev43645 - src/apps/mail

  • From: Clemens Zeidler <clemens.zeidler@xxxxxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 10 Jan 2012 11:23:32 +1300

On Tue, 10 Jan 2012 11:04:33 +1300, <zharik@xxxxxx> wrote:

* Move to the next message after pressing "Unread" button that
  is consistent with corresponding "Unread" button case.
  Fixes #4774;
* Those problems were fixed during completing GCI 2011 task.
Signed-off-by: Siarzhuk Zharski <zharik@xxxxxx>
----------------------------------------------------------------------------
diff --git a/src/apps/mail/MailWindow.cpp b/src/apps/mail/MailWindow.cpp
index f3a723b..e204cb8 100644
--- a/src/apps/mail/MailWindow.cpp
+++ b/src/apps/mail/MailWindow.cpp
@@ -1478,6 +1478,7 @@ TMailWindow::MessageReceived(BMessage *msg)
                case M_UNREAD:
                        MarkMessageRead(fRef, B_SEEN);
                        _UpdateReadButton();
+                       PostMessage(M_NEXTMSG);
                        break;
                case M_READ:

I don't see why this is a good idea. For the read case it is obvious that I'm done with the message and want to see the next one. For unread the user may still continue reading. My workflow would be that I search a important message, mark it as unread first and then possible take a another look at that mail.

Regards,
        Clemens

Other related posts: