>>>>> "LJ" == Lolling, Jan <[EMAIL PROTECTED]> writes:
LJ> hello, I found a bug in a repaint-mechanismus from batik: If your
LJ> DOM contains less than 3 elements (except lines) and you
LJ> manipulate the position or size of one element than you get
LJ> massive repaint-errors: On canvas you see any fragments from all
LJ> elements in wrong locations. After a reset from the current affine
LJ> transformation the images is correct.
LJ> If your canvas contains more than 2 elements than this error don�t
LJ> occurse.
LJ> This behavour is stabil also in the current version (HEAD) from
LJ> CVS repository (xml-batik).
LJ> Here a svg-code to provoke the error:
This is a static image. It can't possibly have repaint errors. :)
Since I think you are modifying the content from Java my suspicion
is that you have a race condition (you are updating the DOM while the
image is being rendered). I can say that I have _never_ encountered a
repaint error since we first got it working (excluding filters which
dynamic updates aren't supported for yet).
Can you provide a standalone java file that shows the problem?
LJ> <?xml version="1.0" standalone="no"?> <!DOCTYPE svg PUBLIC
LJ> "-//W3C//DTD SVG 1.0//EN"
LJ> "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd";>
LJ> <svg width="450" height="500" viewBox="0 0 450 500"> <rect id="s1"
LJ> x="10" y="10" height="40" width="50" stroke="black" fill="white"
LJ> /> <rect id="s2" x="100" y="100" height="20" width="20"
LJ> stroke="red" fill="none" /> </svg>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
