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 <[email protected]> wrote: > 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 <[email protected]> wrote: > > > Hi, > > > I'm trying to create an activity which would be on top of other > > activities (a small dialog themed activity) and I want to get ALL key > > events to be ignored by my activity and handled normally by the > > activity beneath it. > > When I say all I mean the send, end and back keys too. > > > Is this possible? > > > I've tried setFocusable(false), setting the flag FLAG_NOT_FOCUSABLE, > > and adding a dummy onKeyListener but nothing doesn't seem to do the > > trick. > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
