Axel Hahn - 2016-05-17 21:27:36 - In reply to message 1 from Cleverson Rodrigo Oliveira
thanks for your report.
If I look at developers.google.com/maps/document ...
here the zoom level (methods getZoom() and setZoom(value)) is a *number* (not a float). Using +/- buttons on lower right changes the zoomlevel +/-1.
Hm. Maybe it is a kind of a undocumented feature to use a float zoom level that "just works" on Google?!
If somebody should be sure about it I would be happy to get a comment.
Cleverson Rodrigo Oliveira - 2016-05-19 19:28:30 - In reply to message 2 from Axel Hahn
I used the mouse scroll, not the buttons. Perhaps the operation is different.
However, when we provide a tool for users, it is extremely frustrating when returns an error, so we should take every precaution.
Axel Hahn - 2016-05-22 18:49:43 - In reply to message 3 from Cleverson Rodrigo Oliveira
OK, I see it. Thanks for your hint.
I can offer to parse the zoom level as float in the first step.
But OSM cannot handle these zoom levels as float and redirects to an integer zoom level. So the optical results of 2 generated links can differ. This can be an unwanted behavior in some cases.
So I need to add something to use a strict mode or a lazy one and send it in an additional return message/ return code.
I also saw the maximal zoom level differs between map service providers (Yandex: 18; OSM: 19; Google: 21).
This must be added too.
I hope these suggestions fit your needs. Otherwise let me know.