[113] in java-interest
Re: Input "meltdown" in AWT
daemon@ATHENA.MIT.EDU (Scott Hudson)
Wed May 24 11:19:00 1995
From: hudson@cc.gatech.edu (Scott Hudson)
To: java-interest@java.Eng.Sun.COM
Date: Tue, 23 May 1995 12:32:46 -0400 (EDT)
Previously I had written about a serious problem with unbalanced input and
output in AWT and said:
> The problem seems to lie in the fact that the updater thread spawned
> in awt.DisplayItemWindow.startUpdater() gives itself a priority of
> NORM_PRIORITY-1 (at awt/DisplayItemWindow.java:536), whereas input is
> handled by the main thread with priority NORM_PRIORITY.
>
> A quick fix may be to just leave the updater thread at the same
> priority as the input thread (haven't had a chance to try that yet).
> However, I think that the "right" fix is a bit more complex.
Unfortunately, it doesn't look like leaving the priority of the
updater thread at NORM_PRIORITY has any effect on this. What I did was
simply to comment out line 536 of awt/DisplayItemWindow.java (and put
in a println to ensure I was loaded and executed properly). Maybe
someone involved with writing this code and offer a simple explanation
as to why.
I will continue to look into fixes for this...
Scott Hudson
http://www.cc.gatech.edu/gvu/people/Faculty/Scott.E.Hudson.html
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
