John,
I had a similar problem a while ago and had to change a line inside BufferedLayer.projectionChanged(com.bbn.openmap.event.ProjectionEvent pe).
The original was
mapBean.setProjection(proj);
I changed this to
mapBean.setProjection(proj == null? proj : proj.makeClone());
I think there is a threading issue where, if you trigger many projectionChanged events one after the other, mapBean will sometimes mutate the projection object before the BufferedLayer has processed the previous projection event. I don't remember exactly why this was a problem, but it had something to do with the layer deciding that the new projection was the same as the one it had before, and ignoring the projection event.
-Ben
PS. I'm attaching the changed file.
________________________________
From: owner-openmap-users_at_bbn.com [mailto:owner-openmap-users_at_bbn.com] On Behalf Of john.kimball_at_att.net
Sent: Thursday, July 17, 2008 5:35 PM
To: openmap-users_at_bbn.com
Subject: [OpenMap Users] BufferedLayer occasionally fails to repaint in version 4.6.4
I have an OpenMap-based application that uses a BufferedLayer containing a GraticuleLayer and two ScaleFilterLayer instances, each containing ShapeLayers, one with edges/boundaries and the other with filled areas of political regiions..
When zooming in and out the BufferedLayer occasionally (1 time in 10?) fails to repaint, and only the map background and our custom graphics are shown.
The application did not exhibit this behavior in version 4.6 with the same layers and layer configuration.
Removing the component layers from the BufferedLayer and displaying them separately solves the failure to repaint problem, but map update rates for our graphics are unacceptable.
Anyone have any suggestions?
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Fri Jul 18 2008 - 11:20:40 EDT