George Armhold wrote:
My current understanding of the batik threading model is that one can
expect the UpdateManager to be available once gvtRenderingCompleted
has been fired. This has always worked great for me. But now I am
trying to "prepare" my canvases in advance by constructing them and
calling setSVGDocument before they are made visible on the screen. I
notice that gvtRenderingCompleted is never fired until the canvas is
made visible in some displayed component. Is there some workaround
for this?
Perhaps....
Would waiting for gvtBuildCompleted suffice, to access the UpdateManager?
Definitely not.
For what it's worth, what I am trying to do here is write a
synchronous version of setSVGDocument- the caller should block until
the doc is fully loaded and ready. (Yes I am taking care not to block the Swing EDT.)
If you are just interested in knowing "the last thing" before rendering you should wait on the 'svgLoadEventDispatchCompleted'. At this point however there will not be installed untill the first rendering completes (after all you can't update something that doesn't exist).
If you want the update manager so you can twiddle the document you can (and should) do this in an onload DOM event handler (perhaps attached after document load) or in one of the svgLoadEventDispatch callbacks (so if you do it in the Completed call you will know that any 'in document' onload handlers have run and completed).
I'm not 100% sure that I understand what you want to do so let me know if I've missed something important.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
