[android-developers] Re: Passing keyevents to the next activity in the stack

Hi, As I've said before I used superDispatchKeyEvent to get around the not responding issue I was getting when setting my app to NOT_FOCUSABLE. But I still wonder how can I set an app to be NOT_FOCUSABLE (using setFlags) but not get a "not responding" window whenever I press some key and wait for

[android-developers] Re: Passing keyevents to the next activity in the stack

Thanks Dianne, The NOT_FOCUSABLE flag caused my app to be mistakenly recognized as not responding, I think the OS expected me to handle keys even when I'm not focusable. I eventually got what I wanted using superDispatchKeyEvent. Thanks again, Mor. On Apr 4, 11:28 pm, Dianne Hackborn wrote: >

[android-developers] Re: Passing keyevents to the next activity in the stack

Setting FLAG_NOT_FOCUSABLE on the window should probably work. Make sure you are setting it before you add your content view, and using the API to add flags instead of just directly poking the LayoutParams structure. On Sat, Apr 4, 2009 at 9:43 AM, marmor wrote: > > Hi, > > I'm trying to create