For future readers - The problem described in the above posting was a side effect of using a ListView incorrectly. We were keeping references to the Views inside the individual rows of a ListView. This conflicts with ListView's internal View caching and recycling. We replace that with a LinearLayout inside a ScrollView and the problems with apparently delayed clicks went away.
On Nov 14, 9:23 pm, jotobjects <[email protected]> wrote: > We are still seeing this - several clicks are "ignored" and then > suddenly they all fire so we wind up doing several startActivity() > calls in a row in the onclick() method. > > What is the cause of this and how to fix it? Anybody? > > On Nov 12, 8:29 am, jotobjects <[email protected]> wrote: > > > The app I am working on is having this strange behavior - It works > > correctly for a while, but after some series of actions (that I'm not > > sure how to replicate) it does this - > > > - seems to stop responding to clicks on some ImageViews that have > > OnClickListener() set. These methods call > > context.startActivity(intent) > > > - later after clicking on some other button (or going to Home screen) > > all the startActivity intents fire off (this can be seen in the log). > > Then the last of the Activities comes to the front and the Activity > > stack has all the Activities which you can go back to with the Back > > key. > > > Does anybody recognize this scenario? Any ideas what might be wrong? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
