From a724df79d4afb5f3c85b311f63a2635f5550ce17 Mon Sep 17 00:00:00 2001
From: Jesse Vincent <jesse@fsck.com>
Date: Sun, 8 Aug 2010 23:49:27 +0000
Subject: [PATCH] To date, "loadMessageForView" competed for threads in a
 thread pool with all of our mail syncing code. This led to very choppy UI
 experience.

This change doesn't entirely fix message load lag, but the _worst case_
I see is now better than the best case I saw last week.
---
 src/com/fsck/k9/controller/MessagingController.java | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/com/fsck/k9/controller/MessagingController.java b/src/com/fsck/k9/controller/MessagingController.java
index c96af7fd8..887daf824 100644
--- a/src/com/fsck/k9/controller/MessagingController.java
+++ b/src/com/fsck/k9/controller/MessagingController.java
@@ -3094,7 +3094,7 @@ public class MessagingController implements Runnable
         {
             l.loadMessageForViewStarted(account, folder, uid);
         }
-        threadPool.execute(new Runnable()
+        new Thread(new Runnable()
         {
             public void run()
             {
@@ -3152,7 +3152,7 @@ public class MessagingController implements Runnable
 
                 }
             }
-        });
+        }).start();
     }
 
     /**