Did you try:
JSVGComponent.setDocumentState(JSVGComponent.ALWAYS_DYNAMIC);
That should ensure dynamic updtes are always done and that will avoid that your DOM is scanned everytime you do a setSVGDocument to detect whether it is dynamic or not (see what AUTODETECT does).
Vincent.
[EMAIL PROTECTED] wrote:
Hi All,
Is there any particular difference between JSVGCanvas.setURI() vs. JSVGCanvas.setSVGDocument() in terms of dynamic DOM updates? Some background.... In my application, the user can choose between 2 SVG displays. Upon startup, I use setURI() to load in the SVG files. Once I've loaded in the SVG files by using setURI(), I cache the SVG Documents that are generated. So the next time the user wants a particular SVG display, I just use setSVGDocument() with the parameter being one of my cached SVGDocument objects. I do this to avoid redoing time consuming tasks, such as reading in the SVG from file.
My problem is the following... When I use setURI(), dynamic DOM updates are correctly being reflected in the JSVGCanvas. However, when I use setSVGDocument(), dynamic DOM updates are not being reflected in the JSVGCanvas. In particular, changing the "fill" attribute of text nodes is not updating correctly for me when I use setSVGDocument(). Any insights? Thanks!
-Shawn
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
