Jorg Heymans wrote:
Then when it goes to updateRenderingTransform it get's a bit confused.
Probably the best way to work around this problem would be for you to create a new SVG element rather than update the root SVG element.
This can be done by simply creating the element: <svg x="0" y="0" width="100%" height="100%" viewBox="# # # #"> and appending your new content under it.
This is a workaround, but i've got code like
getSVGDocument().getRootElement().getScreenCTM().inverse().getE();
, which will produce invalid numbers after I modify the viewbox in a different element, right ?
Yes, but this is easily fixed by adding an 'id' to the new svg element and replacing 'getRootelement' with getElementById('foo') (where 'foo' is the id on your new SVG).
I'm trying to think of good solutions to the underlying problem. Can you give me a ball park figure for the 'updated' viewBox coords? I'd like try and produce a simple standalone example of the problem.
An updated viewbox is for example 423463.2 -5470604.7 133015.10000000003 113988.29999999981
As I suspected the range is vastly different. Another possible workaround would be to set 'recenterOnResize' to false on the canvas (canvas.setRecenterOnResize(false)). I think this will solve the problem if my suspicions are correct.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
