Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Mar 2006 20:24:04 -0500
From:      Sergey Babkin <babkin@verizon.net>
To:        Greg 'groggy' Lehey <grog@FreeBSD.org>
Cc:        "Rick C. Petty" <rick-freebsd@kiwi-computer.com>, FreeBSD Hackers <hackers@freebsd.org>
Subject:   Re: Programs not accepting input?
Message-ID:  <4429E1B4.DDF52803@verizon.net>
References:  <19770339.131791143464603498.JavaMail.root@vms075.mailsrvcs.net> <20060328011345.GC25392@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey wrote:
> 
> > The focus management and the highlighting of the window manager
> > decoration are not physically connected in any way, so a bug in the
> > window manager might cause it to do the highlighting but forget to
> > give the focus to the application.
> 
> But mouse focus and keyboard focus are the same, right?  The windows
> respond to the mouse, but not to the keyboard.

There is no mouse focus. The mouse events are delivered to whatever
window happens to be under the mouse pointer. Well, unless a 
pointer grab is in effect, but that's a separate story.
 
> The remainder of your reply seems to build on the assumption that
> there is no focus.  I'll leave it there in case I misunderstood and
> you want to refer to it.

No, the remainder describes the case when the focus works correctly
but the mapping from keycodes to keysyms gets somehow broken, so that
the app gets the keyboard events but then it can't translate them
into the text strings.

Sorry, I couldn't look for the programs yet.

-SB
 
> > To debug that you can add debugging printout to the WM. Or I've had
> > a script that sort of decoded the X protocol, so if you can get the
> > dump of these (maybe with ktrace), you can decode the dump and see
> > what happens with the focus. I'll look for it in my archives.
> >
> > If no, it might be something with the keyboard event translation to
> > keysyms/text. You can debug this by writing a test program that
> > would do it own dispatch loop - i.e. call XEvent() and then
> > XtDispatchEvent() (or some close names - I might not remember them
> > right), and print the debugging messages. So if you see that
> > XEvent() is getting events but then nothing comes out of dispatching
> > them, then the translation is broken somewhere.
> >
> > I might be able to find this kind of a program
> > in my archives too, I'll look around.
> 
> thanks.
> 
> > BTW, one place where the keyboard events might disappear is the
> > Input Method handling code. But I don't think that you run any Input
> > Methods.
> 
> Not explicitly.
> 
> Greg
> --
> See complete headers for address and phone numbers.
> 
>                                                   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4429E1B4.DDF52803>