Thomas DeWeese wrote:
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.
Thank you! In the meantime, I found the NoRepaintInterface, too, and
this solves my problem. Is one of the two solutions the "better one"?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
