I wrote previously:

> I used the change in the second message, and it works. Amazing!
>
> So I can now abandon openbox and go back to ctwm.
>
> However, I had to do some extra work to make the keyboard work as it
> did previously.
> .....

I have found another strange thing since ctwm was changed, though I
have not tried to find out what causes this by undoing various
changes to the source.

There are some programs, e.g. glxgears and the demos of the ode
(open dynamics engine) that start up with a graphic window, but
should be able to accept keyboard input.

Since I've gone back to the revised ctwm, these programs have not
accepted keyboard input if started from a command an xterm window if
they (e.g. the glxgears window) appear on top of the xterm window.

However if I move the graphical window onto the root, then move the
mouse in the root then into the graphical window it gets the
keyboard focus. The graphical window does not have to be entirely in
the root window, as long as a portion of it overlaps the root, so
that the mouse can enter from the root.

It was very annoying at first because I could not find any way to
get get keyboard input into these programs, but now I know that they
get the focus if entered via root I can live with this.

I have tried turing various ctwm variables that deal with focus on
and off, but it makes no difference.

It is not restricted to the graphical window coming up over an xterm
window. If it comes up over xpdf I get the same behaviour --
keyboard input works only if mouse comes in via an window edge on
the root.

I don't know enough about x11 programming to have any idea what the
cause may be.

Aaron
http://www.cs.bham.ac.uk/~axs

Reply via email to