DO NOT REPLY - Batik calls repaint() while not running in Swing thread

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41
165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41165


deweeseapache.org changed:

           What    |Removed                     |Added
------------------------------------------------------------
----------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From deweeseapache.org  2006-12-22 03:08 -------
Yes, Deiter is correct.  'repaint()' is one of the few
methods that is
documented as being thread safe:

  The following is from this URL:

http://java.sun.com/products/jfc/t
sc/articles/threads/threads1.html#exceptions

The following JComponent methods are safe to call from any
thread: repaint(),
revalidate(), and invalidate(). The repaint() and
revalidate() methods queue
requests for the event-dispatching thread to call paint()
and validate(),
respectively. The invalidate() method just marks a component
and all of its
direct ancestors as requiring validation.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=ema
il
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the
assignee.

------------------------------------------------------------
---------
To unsubscribe, e-mail: batik-dev-unsubscribexmlgraphics.apache.org
For additional commands, e-mail: batik-dev-helpxmlgraphics.apache.org