Hi, I spent the last few days testing the current trunk version for flaws on refresh, newModel and loadModel. The result was that hardly any map widgets handle those events correctly. So I added additional checks, new or improved clear methods for newModel events, and custom destroy actions for OpenLayers classes.
I also did some restructuring of the edit buttons to comply with the MVC pattern, and changed MapPaneOL to always add an empty baselayer. This is not only good for the layer control, but also a logical step because MapContext and OwsContext do not have a concept like the baseLayer in OpenLayers. Finally, there should be less memory leaks now, although I did not check yet with Drip. I would be glad if other devs could also test the new trunk with their applications, but there should not be anything broken. If you are all satisfied with my fixes, I would propose to add them to the 1_5 branch. Regards, Andreas. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
