xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yaroslav Bulatov" <yarosla...@gmail.com>
Subject Re: bug with invokeLater?
Date Tue, 14 Nov 2006 18:53:50 GMT
> Hi Yaroslav,
> "Yaroslav Bulatov" <yaroslavvb@gmail.com> wrote on 11/08/2006 08:44:04 PM:
> > Another place that waits on the list is the RunnableQueue.invokeLater()
> method.
>    No invokeLater does not wait on the list.  It synchronizes on it, you
> don't have to notify a thread that is blocked on a synchronize, it will
> drop through when the resource becomes available.
> > So wouldn't it deadlock if I do
> > canvas.getUpdateManager().getUpdateRunnableQueue().invokeLater() while
> > the runnableQueueThread is running?
>     No, I don't think so.  There is a problem if you use
> invokeAndWait from the Swing thread but AFAIK invokeLater doesn't
> have (and hasn't had) deadlock issues.

I'm calling it from the thread called "AWT-EventQueue-0", more
specifically it's getting called when "gvtRenderingCompleted" is
called on GVTTreeRendererListener....is that a problem?

To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org

View raw message