- From: Jonathan Watt <jonathan.watt@strath.ac.uk>
- Date: Sat, 12 Jun 2004 11:37:46 +0100
- To: www-svg@w3.org
Cameron McCormack wrote: > Hi Jonathan. > > Batik doesn't keep a reference to the SVGMatrix passed in to setMatrix, > it just uses the SVGMatrix to modify the SVGTransform's internal > representation of the transformation. And when the matrix attribute is > referred to a new SVGMatrix object is returned. But modifying this new > SVGMatrix object still does affect the SVGTransform. > > This sort of thing happens a lot in the Batik code. In this case, when > you refer to the matrix attribute of the SVGTransform an instance of an > anonymous class inheriting from AbstractSVGMatrix is returned, whose > setA..setF methods affect the SVGTransform. > > Cameron Hi. Thanks for the clear reply Cameron. It's interesting to know how Batik works, as well as how it behaves. :) Jonathan
Received on Saturday, 12 June 2004 06:37:50 UTC