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, 10 Oct 2003 11:43:20 GMT
George Armhold wrote:
> Thomas DeWeese wrote:
>  > Hmm, there is a problem with this.  The BridgeContext isn't disposed
>  > of until after all the managerStopped Listeners have been called.  I
>  > don't think this is correct behavior, but until it's fixed you will
>  > actually have to hang your listener off the document load or gvt
>  > build listener to make sure the old document is no longer 'active'.
>  >>
>  >> You mean I should install this listener after (say) gvtBuildCompleted?
>  > No I meant you will need to use the gvtBuildCompleted event to know
>  > that your oldDoc is 100% disentangled from the Canvas.  You should
>  > probably also catch the build failed (problem with doc), and build
>  > canceled events as well.
> Sorry, but I don't quite understand how waiting for gvtBuildCompleted
> fixes the problem with the BridgeContext.  

    I should have said gvtBuildStarted (although completed would work it's
later than it needs to be).  The problem is that the BridgeContext
isn't disposed of (which completes the disentanglement) until shorty
_after_ all the UpdateManagerStopped events are delivered.  So what I
am suggesting is  waiting for the first event after UpdateManagerStopped so
you know that the Canvas has disposed of the BridgeContext for the previous

    I will probably fix this problem with BridgeContext disposal shortly
(over the weekend) so you could just wait for that (I think
UpdateManagerStopped should signal that the Canvas is done with the document).

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

View raw message