Thomas DeWeese wrote:
Ok, I think I know what is happening. The canvas 'caches' a copy of the viewingTransform so it doesn't have to go into the UpdateManagerThread to access it everytime. The problem is that when you change the viewBox this copy is now invalid.
makes sense.
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 ?
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
Thanks Jorg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
