I tried this on RH9, got the same problem. So, either it's a java bug,
or something I've done wrong. Of course, it couldn't be me, so it must
be a java bug.
I'll see if I can write an example.
-Charles
Charles Lockhart wrote:
Now I've bumped up to jre 1.42, and the
thread problems have gone away, but now I'm having some AWT widget/event
oddities (example: a client gets feedback that a state changed on the
server, and then calls the select() function on a choice widget. Calling
select() shouldn't generate an event, but it does, and the event then
changes the value on the server, which then calls back to the client to
update, which generates an event, and so on forever). I'm testing to
see if I'd have these problems running the newer jre on a rh9 machine
(they didn't show up on my rh7.3 machine).
