Skip to content

Report camera fov and apply paddings - #31

Merged
wf9a5m75 merged 2 commits into
developfrom
feat/camera-paddings
Nov 12, 2026
Merged

wf9a5m75 merged 2 commits into
developfrom
feat/camera-paddings

Conversation

@wf9a5m75

Copy link
Copy Markdown
Contributor

Summary

This provider now

  • reports MapCameraPosition.fov for its engine, and
  • honours MapCameraPosition.paddings on move / animate: the target lands at the centre of the padded area, and the camera read back reports the target with the same paddings.

Depends on the core feat/camera-paddings PR (and, where noted, the provider's tilt fix PR).

fov 30 (measured in portrait, landscape and half size); paddings emulated (native setPadding jumps at the start of animations and moves the logo).

Commits

  • Apply camera paddings and report fov on Google Maps
  • Merge remote-tracking branch 'origin/develop' into feat/camera-paddings

GoogleMap.setPadding is not used: it shifts the view the moment it is
set, so an animated move jumps at the start, and it also moves the logo
and controls. Paddings are emulated by moving the camera center with
CameraPaddingEmulation and undone when the camera is read. fov is 30
(Google has no API for it; measured 30 on TB520FU portrait, landscape
and half size, unlike the ~25 of the JS vector map).
@wf9a5m75
wf9a5m75 merged commit 858c316 into develop Nov 12, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant