Thomas, that's true. The rendering is scheduled again, but when there is a resize in the second run it looks as if it always goes into failed, i.s.o. cancelled.
My aim is however to prevent the resize completely, because it's a wast of time to do the rendering twice ( .. isn't it ??). Is there a way to have batik wait for that, or should I take care of that in Swing? I'm trying to understand the rescheduling: in AbstractJGVTComponent I see a listener for a component resize that reschedules the rendering, however it checks for updateRenderingTransform() which always returns false. Am I missing something?? Vincent > > This shouldn't really be a problem because it should queue another > render request. Is that not happening for some reason? > > > -- View this message in context: http://www.nabble.com/how-to-handle-resize-tf2129806.html#a5941300 Sent from the Batik - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
