[android-beginners] Re: stubborn error wont go away

2010-07-20 Thread DanH
Yeah, same here, but they are handy in some cases. On Jul 19, 11:18 pm, Justin Anderson janderson@gmail.com wrote: * Yeah, the ability to define a class inline like that is a very powerful feature of Java, but it can be very confusing since the {} and () get nested so deeply and get so

Re: [android-beginners] Re: stubborn error wont go away

2010-07-20 Thread TreKing
On Mon, Jul 19, 2010 at 1:18 PM, martinmike2 martinmi...@gmail.com wrote: not sure what im doing wrong. This: Im just starting app development and learning java at the same time. Do yourself a favor and learn Java first independently of Android. It will be much easier to get your pants on

[android-beginners] Re: stubborn error wont go away

2010-07-19 Thread martinmike2
I should probably give some info background here. The code is listening for a button click to call a private function searched(String sTERM). Im just starting app development and learning java at the same time. not sure what im doing wrong. -- You received this message because you are

Re: [android-beginners] Re: stubborn error wont go away

2010-07-19 Thread Justin Anderson
Your call to setOnClickListener is missing a closing parentheses... which is why you get the error telling you to insert one. -- There are only 10 types of people in the world... Those who know binary and those who don't.

[android-beginners] Re: stubborn error wont go away

2010-07-19 Thread DanH
Yeah, the ability to define a class inline like that is a very powerful feature of Java, but it can be very confusing since the {} and () get nested so deeply and get so distantly separated. On Jul 19, 1:31 pm, Justin Anderson janderson@gmail.com wrote: Your call to setOnClickListener is

Re: [android-beginners] Re: stubborn error wont go away

2010-07-19 Thread Justin Anderson
* Yeah, the ability to define a class inline like that is a very powerful feature of Java, but it can be very confusing since the {} and () get nested so deeply and get so distantly separated. * Personally, I tend to avoid inline classes for that very reason...