On Jan 7, 10:26 am, Sean Hodges <seanhodge...@googlemail.com> wrote: > The method really depends on your requirements: > > * If the amount of work isn't too great, and you just want the > activity to be drawn before the processing starts, then postDelayed() > is a sensible approach. > > * If you have a lot of processing to do, and the execution needs to be > linear (e.g. (a) must finish before (b) which must finish before (c)) > , then an ASyncTask or Runnable would allow that to happen without > interfering with the activity event loop. > > * If you have a lot of processing to do, but want to split it up into > lots of asynchronous background tasks (and execution order is less of > an issue), then using a message queue would be more manageable. > > If you're unsure which one you will need, then a postDelayed() is a > simple approach to start off with. You could extract intensive work > into background threads later on. > >
imho message queue is better solution than postDelayed() since with the latter you have to pass delayms: 200 could be ok, but maybe 100 would be better, or maybe 50 or 20? it all depends on how complex your view is and how fast/busy your device is pskink
-- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
