There is a rather subtle bug in
WGoogleMap::zoomWindow (const Coordinate &topLeft, const Coordinate
&bottomRight)
...
Coordinate topLeftC = topLeft;
Coordinate rightBottomC = rightBottom;
topLeftC = Coordinate(std::min(topLeftC.latitude (),
rightBottomC.latitude ()),
std::min(topLeftC.longitude(),
rightBottomC.longitude()));
rightBottomC = Coordinate(std::max(topLeftC.latitude (),
rightBottomC.latitude ()),
std::max(topLeftC.longitude(),
rightBottomC.longitude()));
If, say, rightBottomC.lat < topLeft.lat, then after the seconds assignment
to topLeftC, topLeftC.lat == rightBottomC.lat. Then, in the next assignment,
rightBottomC.lat = rightBottomC.lat, so that both lats are equal. Bummer.
The solution should be to use the original parameters in the min/max
expressions.
BTW, calling the parameters botttomLeft and topRight would match
Googles sw and ne.
Or, why not call them anyCorner and oppositeCorner, just to emphasize
that any two opposite corners will do.
/Lars
-------------------------------------------------------------------
Lars Hamrén WWW...: www.sdu.se
Vadmöllan 211 Tel...: +46( 46)189090
S-225 94 Lund Mobile: +46(705)189090
Sweden
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
