xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas DeWeese <Thomas.DeWe...@Kodak.com>
Subject Re: SVGCanvas behaviour between 1.5b5 and 1.5!
Date Fri, 19 Sep 2003 10:36:01 GMT
Jean-Christophe ARNU (JX) wrote:
> Hi all :)
> 	I recently updated my Batik from 1.5b5 to 1.5 for stability purpose (and
> corrections on document handling (nullpointerexception on some kind of
> figures).
> 	I use an SVGCanvas into an panel where components are added to or removed
> from depending on users interactions (including SVGCanvas).
> 	When I used Batik 1.5b5, my SVGCanvas displayed correctly the first time, and
> was redisplayed also when the component was removed then added from the
> container panel a new time...
> 	When I use Batik 1.5, my SVGCanvas also displays correctly the first time but
> remains blank while I perform a remove/add cycle...

    This sounds like a bug that was fixed in CVS, shortly after the release
of 1.5 (to prevent memory leaks it called setSVGDocument(null) on removeNotify).
It no longer does this - but applications should now call 'dispose()' to clear
heavy resources from the canvas when they are done with it.

> 	The only things I can (for a first mail) say to help (maybe) is that my
> document is set ALWAYS_DYNAMIC, some parts of the document are dynamically
> added after load, that NO EXCEPTION are produced during runtime...
> 	Does it sounds like a deja-vu behaviour? What may have I forgotten to set (or
> unset) in my SVGCanvas setting?
> 	Thanks in advance!

To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-users-help@xml.apache.org

View raw message