Hi Erich,
> I figure I could work with two SVG components and just keep one in the > background or so... Yes, working with two components seemed like the simplest way to workaround the unexpected behavior. Just to clarify: when you mean components you are meaning JSVGCanvas right? > what other options do I have for updating the SVG > document asynchronously without losing updates whenever I call > setDocument()? I don't know. I'd say this could be a Batik issue. It would surely help if you could generate a reduced test case and attach it's source code to a follow up...? Somehow related, you don't state anything about your environment: Batik version (or trunk revision) would be the absolutely minimum; Java version, operating system, etc. could also help... Note that this is a tentative answer: I was hoping one of the Batik developers (Thomas? Cameron?) would be able to give more interesting feedback. Trying to provide more details (possibly code snippets, steps to reproduce the behavior, etc.) might also increase the possibility of receiving more replies. ;-) Hope this helps, Helder --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
