I've submitted it now as issue 1705: http://code.google.com/p/android/issues/detail?id=1705
In my own app I now use a ListView to replace Menu altogether, and that finally works. Regards On Dec 30 2008, 3:12 am, Enginerd <enginer...@gmail.com> wrote: > I'm having a similar issue. I guess you could set up listeners for > key up/down (and/or scroll), and check to see where thefocusis. > It's tacky, but I think it would work for a simple scroll list. Not > sure if this would work for all phones though, and it would definitely > be a good thing to have. > > On Dec 26, 11:46 am, blindfold <seeingwithso...@gmail.com> wrote: > > > In other words, what is the rationale behind Android lacking something > > like an android.view.MenuItem.OnFocusChangeListener, while there does > > exist an android.view.View.OnFocusChangeListener? After all, the > > ListView - which is functionally not all that different from aMenu- > > supports both a setOnFocusChangeListener() and a setOnItemClickListener > > (). Why wasMenunot designed as a subclass of View such that it would > > have naturally inherited the listeners? Android currently seems to > > lack some key functionality for accessibility. > > > Regards --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
