From bf4e37d3b5b397d084918f4c4fedbc39e050c50a Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Tue, 15 Dec 2009 04:26:53 +0000 Subject: [PATCH] Revert "An attempt to make message lists start displaying messages earlier by precomputing a list item." Sadly, it caused explosions This reverts commit 5b321f4d0893ad5538d229b1c84f6806d0d8cbfe. --- src/com/fsck/k9/activity/MessageList.java | 24 ++--------------------- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/src/com/fsck/k9/activity/MessageList.java b/src/com/fsck/k9/activity/MessageList.java index d69a97900..50dc37410 100644 --- a/src/com/fsck/k9/activity/MessageList.java +++ b/src/com/fsck/k9/activity/MessageList.java @@ -293,7 +293,7 @@ public class MessageList public void onItemClick(AdapterView parent, View v, int position, long id) { - //Debug.stopMethodTracing(); + // Debug.stopMethodTracing(); if ((position+1) == (mAdapter.getCount())) { MessagingController.getInstance(getApplication()).loadMoreMessages( @@ -317,7 +317,7 @@ public class MessageList @Override public void onCreate(Bundle savedInstanceState) { - //Debug.startMethodTracing("k9"); + // Debug.startMethodTracing("k9"); super.onCreate(savedInstanceState); requestWindowFeature(Window.FEATURE_INDETERMINATE_PROGRESS); @@ -343,26 +343,6 @@ public class MessageList mInflater = getLayoutInflater(); - - /* - * Dirty hack - the first time we inflate a message list item - * actually takes a lot longer as Android is doing a fair bit of - * work. Instead of letting that happen when the first item - * is displayed, do it in a thread as we're doing initial setup - * Subjective performance feels a lot better, but who knows. - * - */ - new Thread(new Runnable() - { - public void run() - { - mInflater.inflate(R.layout.message_list_item, mListView, false); - } - - }).start(); - - - mBatchButtonArea = findViewById(R.id.batch_button_area); mBatchReadButton = (Button) findViewById(R.id.batch_read_button); mBatchReadButton.setOnClickListener(this);