On Apr 30, 11:05 pm, Streets Of Boston <flyingdutc...@gmail.com> wrote: > A call to notifyDataSetChanged redraws all the children in the ListView and > is relatively expensive and you get the side effects you notice in your > example (touch issues).
Nobody has yet explained to me how calling notifyDatasetChanged() relatively frequently would cause "touch issues". I am calling notifyDatasetChanged() from the main/UI thread. The touches are coming in and being processed from the main/UI thread. No touches should be lost. Period. When the main/UI thread is busy handling a touch, it should do just that; handle the touch. Nothing else in my code could possibly be interfering with this because my code is also running on the main thread. My data processing code is running in a background thread, but that does nothing worse than notify the main thread in a variable that it may elect to pop data off the data thread if it wants to on a later event loop. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
