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 <william.ferguson...@gmail.com>
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 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
