To cause a widget inside FlutterMap's context to rebuild when the MapCamera, MapOptions, or MapController changes, see #hooking-into-inherited-state.
This page's methods should only be used to listen to events from outside the FlutterMap's context.
When changes happen to FlutterMap's internal state (such as a change to the current MapCamera) it emits a MapEvent, which can be handled by you.
There's two methods to catch all emitted MapEvents. These methods expose the raw MapEvent, and is recommended in cases where multiple events need to be caught, or there's no more specific callback method available in MapOptions (see #catching-specific-events).
Listening to a MapController's mapEventStream, which exposes events via a Stream
Specifying a callback method in MapOptions.onMapEvent
If only a couple of events need to be caught, such as just an onTap handler, it is possible to avoid handling the raw Stream of MapEvents. Instead, MapOptions has callbacks available for the following events:
onTap
onLongPress
onPositionChanged
onPointerDown/onPointerUp/onPointerHover/onPointerCancel
onMapReady
Primarily used for advanced MapController #usage-inside-initstate
The MapEventTap event may be emitted (or the onTap callback called) 250ms after the actual tap occurred, as this is the acceptable delay between the two taps in a double tap zoom gesture.
If this causes noticeable jank or a bad experience (for example, on desktop platforms), disable InteractiveFlag.doubleTapZoom:
This disables the double tap handler, so the MapEventTap is emitted 'instantly' on tap.