The @Override annotation is useful in your case because you will have
a compile time error if you mispelled the function name.
On Sep 29, 5:48 pm, Dipen [EMAIL PROTECTED] wrote:
Thanks Mark.
yes, it was spelling error. Also, i was not calling show() on Toast. I
am little bit surprise eclipse
If you override a function with ctrl+space (or by going into menus),
the @Override will automatically be added, and you can't mispell the
name with auto-completion...
On Sep 30, 3:44 pm, Guillaume Perrot [EMAIL PROTECTED] wrote:
The @Override annotation is useful in your case because you will
Dipen wrote:
public boolean onCreatgeOptionsMenu(Menu menu)
You do not have onCreateOptionsMenu spelled correctly above.
public boolean onOptionsItenSelected(MenuItem item)
You do not have onOptionsItemSelected spelled correctly above.
I do not know if those are real problems or
Thanks Mark.
yes, it was spelling error. Also, i was not calling show() on Toast. I
am little bit surprise eclipse did not catch it. Logcat did not report
any error so, I was constantly paying attention to the logic than
spellings.
Thanks again.
On Sep 29, 11:19 am, Mark Murphy [EMAIL
4 matches
Mail list logo
