Besides implementing those callbacks in the activity, as explained by
Marcin, a frequently occurring pattern is to use anonymous inner classes
at the exact spot where they're needed. Most sample code does something
like this:
void onCreate(...) {
btnCancel.setOnClickListener(new OnCli
Thanks
then I can just use the single std onClick()
Thanks didn't think of that
On Apr 6, 2011, at 8:39 AM, Marcin Orlowski wrote:
>
> On 6 April 2011 13:43, New Developer wrote:
> Within a single Activity.java file I can have
>
> button1.setOnClickListener( new mylistener1() );
> button
On 6 April 2011 13:43, New Developer wrote:
> Within a single Activity.java file I can have
>
> button1.setOnClickListener( new mylistener1() );
> button2.setOnClickListener( new mylistener2() );
> button3.setOnClickListener( new mylistener3() );
>
> and then
>
Use one listener only for a
Within a single Activity.java file I can have
button1.setOnClickListener( new mylistener1() );
button2.setOnClickListener( new mylistener2() );
button3.setOnClickListener( new mylistener3() );
and then
private class mylistener1 implements OnClickListener {
@Override
public void o
4 matches
Mail list logo