Tjorven Lauchardt wrote:
thank you for your help with my othe rproblem, I will come back to that
later. Now, I got to a bigger problem:
I want to change the SVG document, that is displayed by a JSVGCanvas.
So, I put the changes in the run-methode of a new runnable, I add to the
runnablequeue of the updatemanager. After that, I want to transform the
canvas like that:
---
Now, I wich that the state of the document _before_ the transformation
is not painted to the canvas. How can I tell the updatemanager, my
document shall be changed, but not the display?
Uhh, so you want the document update and the rendering transform
change to be treated 'atomicly' no intervening repaint, correct?
If so you have two options:
1) Use the setRenderingTransform(rt, false) before you change
the document this will change the rendering transform but
not cause a repaint event.
2) Have your runnable implement the
batik.bridge.NoRepaintRunable tagging interface (it
extends 'Runnable' so you only need to implement the one).
The update manager won't check if it needs to repaint after
this type of runnable.
---------------------------------------------------------------------
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]
