Recently active topics in Modest Maps

Bug Report: Wrong Calculation of longitude.
Description: Longitude value is wrong if user pan horizontally out of -180---180. This could be a bug comparing to current online product like Google Map...
Steps to Recreate:
1. create a TextField to serve as a status bar to display current mouse's location.
2. Attach MouseMove event to the map, below is a sample function:
_map.addEventListener(MouseEvent.MOUSE_MOVE, onMouseMove);

private function onMouseMove(event:MouseEvent):void
{
var point:Point=new Point(event.stageX, event.stageY)
var loc:Location=_map.pointLocation(point,null);
_status.text="x:"+loc.lon+" y:"+loc.lat;
}
3. zoom map to zoom level 2 or 3.
4. drag the map horizontally so that the tiles are reloaded. you will find the longitude value is out of -180--180.

It seems the root for this problem has something to do with MapProvider.outerLimits

I noticed an issue where the user can click zoom in or out buttons and 'erase' the map when they click past the zoom limits. I tried to ignore clicks past the zoom range, but some clicks can make it in before the zoomLevel is updated on the map. I considered disabling the controls until the action finished, but I rejected this because I wanted the controls to remain responsive.

The animationProcess method in Map has:
grid.allowPainting(__animSteps.length <= 1);
(2 times, but it is commented out for panning, and available for zooming in my version).

Tiles are not redrawn when the map hits a zoom limit because there are more animation steps queued up, and TileGrid throws out the zoomBy calls that would go past the zoom limits.

I put a hack into my copy of the normalizeWell function on TileGrid which seems to do the trick:
...
zoomAdjust = Math.round(Math.log(_well.scaleX) / Math.log(2));
scaleAdjust = Math.pow(2, zoomAdjust);

//trace('This is where we scale the whole well by '+zoomAdjust+' zoom levels: '+(100 / scaleAdjust)+'%');

var newZoom:int = zoomLevel + zoomAdjust;
if (newZoom == bottomRightInLimit.zoom || newZoom == topLeftOutLimit.zoom)
allowPainting(true);

var n:int;
for (n = 0; n < zoomAdjust; n += 1)
...

I think I am reporting a problem more than submitting code to be used- there must be a cleaner way to handle this, but I hope this helps someone else.

After a while, google starts to deny loading of tiles, and gives the message: We're sorry, but your query looks similar to automated requests from a computer virus or spyware application. How can I prevent this from happening?

I noticed that Google changed their URL for aerial images. URLs now start with khm# rather than kh# (although kh0 appears to still work)