[EMAIL PROTECTED] wrote:
Additionally it might be good to document that AWTRenderer (and obviously
all subclasses) are not threadsafe.
In some sense, it already is.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
After some debugging and quite some time to get information on the
implications of multithreaded access to AWT/Swing classes, I came to the
following conclusion:
To keep thread-safety in Swing/AWT rendering operations can only be called
from one thread - normally this is the AWTEventDispatchThre
