Felmey, Jonathan wrote:
I have recently taken over a project that is already using Batik within a Java Applet, so I am by no means an expert on batik. The problem I have is that the SVG document doesn’t seem to get updated on the screen until I run my mouse over the areas where there are mouseover events.
This sounds like you aren't using the UpdateManager runnable queue to make your changes to the document.
The document basically gets updated based on data that is being interpreted by the java code in the background. The documented is updated when new data is found. But I don’t see the updates unless I mouseover that particular part of the document. Also I have changed the static parts of the document in a text editor and those parts are still showing up as if I never made a change. It’s as if the document is being cached.
If you change the document on disk it won't automatically reload the document from disk. But I don't think this is what you are talking about.
Is there a way using batik to ensure the document is reloaded each time it is displayed?
Well Batik does do some caching I haven't seen this be a problem with SVG documents (it is occasionally an issue for raster images). In general the caching is all thrown away when a new document is loaded (and the cache is not currently shared between documents). For SVG documents this takes place in the batik.bridge.DocumentLoader class.
Any ideas as to what my problems might be?
Thanks in advance.
Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
