Fixed
Status Update
No update yet.
Comments
br...@gmail.com
Tentatively, the annotation should be something use-case-specific like @OutlinedNewApi that allows alternative build systems (e.g. not R8/D8) to make their own decisions. We'll provide a default Proguard configuration for R8, but it's not guaranteed this will work as intended -- outlining is automatic in newer versions, but it may be disabled.
Description
- Custom Map Type with maxZoom set to 5.
- Standard map (SATELLITE or ROADMAP) with default maxZoom of 19 or 24
(doesn't matter, as long as it's different than whatever custom map is set
to).
- Event attachment on 'maptypeid_changed'.
- Initialize the default MapTypeId to the Custom Map Type.
Bug Description:
When the map type is changed (via the map type control buttons) and the
'maptypeid_changed' event fires, setting map.setZoom(aNumber); to a number
greater than the maxZoom of the *former* map type (9 for example) results
in the new map type being displayed at 5, the *former* map's maxZoom
level, not 9 which would respect the *new* map's maxZoom level. To verify,
I can, before the onEvent function exits, execute the map.getZoom()
function which will reports 5 instead of the 9 that it was set to a few
lines above.
In the attached file, the map starts on CoordMapType. Changing to
SATELLITE should set itself to zoom level 9, but instead it sets to 5.
Changing from SATELLITE to ROADMAP works as expected (setting to 9) since
the *former* map (SATELLITE) already has the level 9. The results are
printed live to the div#Debug below the map for convenience.