stage.focus = null; However, the FocusManager may fight to put the focus somewhere.
Yeah, I recall that you were adding priority as int.MAX_VALUE. Did you try it with default priority? I'm not sure if there are issues using MAX_INT as priority. Do you have default wmode or are you using some other wmode? Are there other focusable widgets in the HTML wrapper? When you only see keydown and no keyup, is the control with focus responding? If you put a target phase listener on that control is it reporting the KEY_UP event? -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Troy Gilbert Sent: Tuesday, March 04, 2008 9:00 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Global keyboard capture? > So - in reality... your implementation may determine which is better to use. > But I do have something for you that might help. If you are having problems > with the capture/bubbling/target phases you probably need to add two > listeners as... You should've read all the way back to my original post... the code I posted was adding exactly that to the stage (with the addition of being highest priority as well). @Alex: could I force keyboard focus to the stage using something like stage.setFocus()? Troy. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links
