Closed GoogleCodeExporter closed 8 years ago
Option: regulate by size of the log tables instead of time.
Original comment by case.and...@gmail.com
on 1 Jul 2010 at 2:12
Original comment by case.and...@gmail.com
on 6 Jul 2010 at 2:20
at least could you please sort it by time, or provide the way to clear the log.
please!
Original comment by sv767%ny...@gtempaccount.com
on 8 Jul 2010 at 5:30
Comment #3 is already done. It is sorted by time (top is the most recent).
And if you click the menu you can clear any/all the logs.
Original comment by case.and...@gmail.com
on 8 Jul 2010 at 2:37
:D:D how retarded am i, thanks
Original comment by sv767%ny...@gtempaccount.com
on 8 Jul 2010 at 6:14
This should probably get resolved before release becuase if users don't view
logs for a long time or don't clear the logs it will make the Logs activity too
slow to open and present a "Force close or Wait" dialog.
Original comment by case.and...@gmail.com
on 17 Jul 2010 at 8:45
These posts about managing limits using triggers have some good ideas. I'll
take a look and see if I can implement this within android:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg12121.html
http://stackoverflow.com/questions/1837993/how-to-set-trigger-on-contacts-databa
se-in-android
Original comment by case.and...@gmail.com
on 17 Jul 2010 at 9:44
Codereview is here: http://codereview.appspot.com/1855053/show
I think time to load 24 hours worth of logs is still too long. We need to look
at a way to optimize the tabbed log activity. Several things could be looked
at:
0) Optimize the sorting in All Logs view as it is the slowest since it loads
logs from all three tables
1) Use ConvertView in the listview
2) Do proressive loading of the listview (see
http://mylifewithandroid.blogspot.com/2010/03/progressively-loading-listviews.ht
ml)
3) Don't reload the listview data between tab changes
Original comment by case.and...@gmail.com
on 1 Aug 2010 at 9:33
Opened separate issue 153 to address the load time of logs.
Original comment by case.and...@gmail.com
on 1 Aug 2010 at 9:39
This issue was closed by revision r846.
Original comment by case.and...@gmail.com
on 2 Aug 2010 at 5:45
Original issue reported on code.google.com by
case.and...@gmail.com
on 30 Jun 2010 at 5:16