xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Herrn ...@mherrn.de>
Subject Re: When is the UpdateManager definitely available?
Date Fri, 02 Nov 2012 13:53:02 GMT

I must push this mail again.
It now happened again multiple times to me, that the the method
canvas.getUpdataManager() returned null when the gvgTreeRenderer completed.
It happens seldom, but it does happen.

Please see again the code snipped in the quoted text.

Is it a bug in batik? According to the javadoc of the getUpdateManager()
method I would expect that it is guaranteed that getUpdateManager() won't
return null when being called after being informed of rendering completion.

Any help appreciated.

On Fri, Jul 20, 2012 at 03:38:45PM +0200, ml@mherrn.de wrote:
> Hi I am using the following code:
> canvas.addGVTTreeRendererListener(new GVTTreeRendererAdapter() {
>         @Override
>         public void gvtRenderingCompleted(GVTTreeRendererEvent e) {
>           canvas.getUpdateManager().getUpdateRunnableQueue().invokeLater(runnable);
>         }
>       });
> to do some changes in the DOM of an SVG document. I expected that the
> updatemanager is definitely available when gvtRenderingCompleted was
> called.
> However, it now happened at least once that I got a NullPointerException
> on the line
>   canvas.getUpdateManager().getUpdateRunnableQueue().invokeLater(runnable);
> So it seems that there is still no guarantee that the UpdateManager is
> available then. Am I missing something? Must I register on a different
> listener?

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

View raw message