That's right, Larry. There was a bug in my algorithm causing it to misbehave.
Thank you! On Nov 17, 11:02 pm, "geocode...@gmail.com" <geocode...@gmail.com> wrote: > On Nov 17, 12:33 pm, anatoliy <anatoliy.arteme...@gmail.com> wrote: > > > Calling fitBounds(((46.756591257633474, 36.3982043125), > > (47.65223417219914, 37.7165636875))) > > > results in > > > new map bounds=((45.33842010329385, 31.98170040625), > > (49.01065412055726, 42.13306759375)) > > > I was checking if something could happen in between - but could not > > find anything. Is there any logic inside of fitBounds which could do > > slightly different thing than requested? > > fitBounds (while it doesn't say this in the documentation, it probably > should), finds the zoom and center which will display the bounds > provided. It won't necessarily be the same as the input bounds > because zoom levels are discrete. > > -- Larry -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
