xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas DeWeese <Thomas.DeWe...@Kodak.com>
Subject Re: JSVGComponent dynamic DOM update, invokeAndWait threading issue
Date Fri, 19 Sep 2003 22:06:50 GMT
George Armhold wrote:
> Thomas DeWeese wrote:
>> Ahh, yes! The update stuff you are seeing is the 'repaint' of the
>> GVT tree - that also happens in the AWT thread but it is enqueued
>> after the runnable completes.  So a longer runnable could delay the
>> enqueue until after the user presses 'load'.  The question then is
>> why were you getting Null UpdateManager?
> OK, I think we are finally closing in on the problem.  I was assuming
> that when my UpdateManagerListener.managerStarted() was fired, that
> meant that the RunnableQueue was then available.  I guess this really
> just means that the manager for screen updates is now running. 

> So now my question is: how can I know when it's safe to call
>    UpdateManager um = getUpdateManager();
>    RunnableQueue rq = um.getUpdateRunnableQueue();
> and add things to the RunnableQueue?

   It is safe after the first GVT rendering completes.
This is _before_ the managerStarted call back, so this
shouldn't be the problem.  You should have enough
instrumentation in your code now to figure out what
the sequence of events is that leads
to the Null UpdateManager is.

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

View raw message