On Sat, Jan 10, 2009 at 5:00 PM, Kris Maglione <[email protected]> wrote: > On Sat, Jan 10, 2009 at 02:44:55PM -0800, Suraj Kurapati wrote: >> >> The app is jEdit <http://jedit.org> version 4.3pre16. The dialogs are >> the "File Open" (Control-O) and incremental search bar >> (Control-comma). > > Ok, that's the only Java app I have installed (because it's the only one you > report bugs for),
Hehe, sorry about that. That's really the only Java app I use. > and the ^O dialog woks fine for me. I can understand. It feels like the bug occurs randomly sometimes. I wish I could freeze the application in that state and debug what is happening. >> I think I may have narrowed down the problem this morning. I assume >> that wmii reads keystrokes first from X.org and checks for the various >> keybindings. If it doesn't find any, it passes them to the currently >> focused client. > > Nope, it tells the server which bindings it needs and the server sends it > only those bindings (with the exception of chained keys, which require a > grab after the first key press). Ah good! That is certainly more efficient than what I had imagined. > It's more likely that it's somehow not > getting input focus back (or doesn't think it is). Does its titlebar get any > unusual borders? Nope, nothing strange about the borders. I can move the client to the floating layer, or to another view, and bring it back just fine. Mouse clicks and drags work fine also. I suppose mouse focus is different from keyboard focus in X? Thanks for your consideration.
