🚀What's New In v8?

Overview

Here's some highlights:

🎉 Unbounded horizontal scrolling - #1948 & #1969 by monsieurtanuki

We're repeating the trend from v7, and introducing yet another feature that's been continuously requested for longer than we can remember 😂.

Thanks to the hard work of external contributors, you can now pan and fling across the anti-meridian as much as you want (when using the default map projection only). Polygons and polylines also cross the boundary without issues as well, and, alongside markers, will appear on all 'worlds'.

This is the first bounty-funded pull request to flutter_map, thanks to our generous Supporters! We hope to open more bounties in future, but you can also add a bounty on a PR as well (just contact us).

Keyboard controls for map gestures - #1987

Maybe not quite as highly requested as horizontal scrolling, but we think keyboard controls were missing, a fairly obvious hole on desktop and web platforms. So we've added them!

Supports arrow & WASD keys for panning, QE keys for rotation, and RF keys for zoom. All key handlers are based on the physical layout of the QWERTY keyboard, so users using other keyboards will be able to use whichever keys are physically located in the same position. These are all optionally controllable via KeyboardOptions for MapOptions - only arrow keys are enabled by default.

(If you were using flutter_map for developing a game for some reason, this might also be useful 😂)

We've also fixed a major performance bug with simplification on Polygon/lineLayers. If you previously disabled simplification to workaround the bug and improve performance, we recommend considering re-enabling it.

We've also made other changes to improve the experience for your users. Checkout the CHANGELOG for the curated changes, and the full commit listing for all the small details.

flutter_map/CHANGELOG.md at master · fleaflet/flutter_mapGitHub

Curated CHANGELOG

Comparing v7.0.2...master · fleaflet/flutter_mapGitHub

Full Commit Listing

Migration

Migrating to v8 should be pain-free for most apps, but some major changes are likely for plugins.

Some breaking changes have been made. The amount of migration required will depend on how much your project uses more advanced functionality. Basic apps are unlikely to require migration.

Most uses of Point<double> replaced by Offset & Size, Bounds<double> by Rect, and Bounds<int> by (IntegerBounds)

With the exception of some areas, uses of 'dart:math' objects, such as Point, have been replaced by equivalents from 'dart:ui' and Flutter libraries. There's multiple reasons for this:

• These classes have been described as legacy since Feb 2024 in Dart/Flutter, and will be deprecated in future

• This reduces internal casting (which we did a whole lot) and usage of generic types (which are inefficient), which has increased performance by around a millisecond or three (in a simple example)

• The tooling and functionality provided by Dart/Flutter reduce the amount we need to maintain internally (reducing duplication), and work better together (such as easily building Rects from Offsets and Sizes

This breaks a large number of coordinate handling functions, such as those converting between geographic coordinates and screen space coordinates (the changed ones) in the MapCamera. We've also renamed some of these functions to remove references to 'point' and replace them with 'offset'.

Most migrations should be self explanatory. If necessary, you can view the PR to see what happened to a method you were using - there's very likely a close replacement! Some methods have been moved to internal usage only, but there's always easy alternatives.

Some external libraries still use the previous objects, and some of our use-cases are just not yet ready to be replaced by these options yet, so you may still find some of the old objects hiding around the codebase. IntegerBounds is internal only.

TileLayer.tileSize replaced by tileDimension

Just changing the argument identifier should be enough - we've just restricted the type to be an integer. You can't get tiles in fractional pixels anyway!

This renaming is also persisted throughout the internals.