Did you try setting setClickable(false) as well? 2011/7/8 William Ferguson <[email protected]>
> Has no one seen an incidence of this occurring? > I would have said flat out it can't occur except that I see a couple > of instances each day. > > Does this mean that all handler code needs to explicitly check to see > if a button is enabled first before executing its action? > > > On Jul 7, 10:31 am, William Ferguson <[email protected]> > wrote: > > I'm finding that some of my users are occasionally getting a button > > firing twice in rapid succession (less than 100 millis) even though > > the first thing the handler does is to disable the button. ie > > > > button.addOnClickListener(new OnClickListener() { > > public void onClick(View view) { > > button.setEnabled(false); > > // do some stuff. > > } > > > > }); > > > > Is this expected behaviour? > > Ie that the InputEvents (button clicks) stack and will be sent to a > > View even though the View is disabled? > > > > William > > -- > 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 > -- 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
