xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thomas.dewe...@kodak.com
Subject RE: FW: Some anomalies using overlapping SVG canvasses
Date Mon, 15 Dec 2008 12:45:59 GMT
Hi John,

"John C. Turnbull" <ozemale@ozemail.com.au> wrote on 12/15/2008 06:54:22 

> You are a certified genius ? that has fixed all the anomalies!

   Sorry, I would have suggested it sooner but your description
of the problem made me think it was already turned on.

> Are there any drawbacks from setting this property?

    Each canvas uses some extra memory (~4bytes*number of pixles).
On todays systems this usually isn't much of a drawback.

> From: thomas.deweese@kodak.com [mailto:thomas.deweese@kodak.com] 
> Sent: Monday, 15 December 2008 22:25
> To: batik-users@xmlgraphics.apache.org
> Cc: batik-users@xmlgraphics.apache.org
> Subject: RE: FW: Some anomalies using overlapping SVG canvasses
> Hi John,
> <thomas.deweese@kodak.com> wrote: 
> >    Until the top object is done drawing I can't draw the top object. 
> "John C. Turnbull" <ozemale@ozemail.com.au> wrote on 12/14/2008 05:44:20 
> > [JCT] [...] What I?d like to see is that when that request is 
> > made the top object renders with the ?before? state while it?s busy 
> > and then the ?after? state when it?s ready.  That way the underlying
> > animation will not show through at any stage. 
>    If you aren't getting this then you should turn on 'double 
> buffering' in the Canvas: canvas.setDoubleBufferedRendering(true) 
> [attachment "PGP.sig" deleted by Thomas E. DeWeese/449433/EKC] 
View raw message