Hey Alexander,
> Another thing that's a bit strange is the fact that the problems
> seem to go away with icewm, although the behaviour regarding the
> events is the same as seen with ctwm.
Can you still reproduce this at will? If so, based on a bit of poking
around icewm and thinking I have a suggestion.
First, try the latest code out of bzr/git. I don't expect this will
make a difference, but it gives us a baseline. And if that gives the
same failure, try taking out the forcing of input we're doing in
AddWindow(). i.e.:
=== modified file 'add_window.c'
--- add_window.c 2017-02-08 20:40:07 +0000
+++ add_window.c 2017-02-15 08:38:48 +0000
@@ -330,7 +330,7 @@
}
/* XXX Forcing input true? Revisit. */
- tmp_win->wmhints->input = True;
+ //tmp_win->wmhints->input = True;
/* CL: Having with not willing focus
cause problems with AutoSqueeze and a few others
It might be that the whole chain for whatever magic Java is doing
really doesn't get along with us insisting on giving it focus, as a
nice counterpoint to all the other issues we've seen with programs
flipping out over us not giving them focus it didn't ask for...
--
Matthew Fuller (MF4839) | [email protected]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.