I've always felt that disabling should be immediate and automatic. Kind of like the old KSR33 TTY -- when you pressed a key the entire keyboard was locked out until the key was acknowledged.
On Oct 1, 2:20 pm, Pent <[email protected]> wrote: > It gets nicer, they could click other buttons and list items too and > your app gets in > a nice tizzy. > > Is there any case where it's *desirable* to handle widget fiddling > after > calling startActivity ? If not, it would be simply wonderful if > Android > would disable all the controls as soon as startActivity is called. > > Pent > > On Oct 1, 6:53 pm, DanH <[email protected]> wrote: > > > If I have a button that starts an activity, and the activity sometimes > > takes a second or two to throw up its own view, how can I most simply > > and reliably protect against the button being clicked multiple times > > and kicking off multiple (identical) activities? -- 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
