mootw

@TheLastGimbus on your issue #824 and PR #826 you were able to fix by adding caching. I am working on a re-write of the state system to improve performance overall...

Made breaking changes to state management. Behavior is almost the same as before, but the name has changed and internally it is much different. This means I will need to...

@TheLastGimbus More or less all you need to to do migrate is remove the plugin wrapper class; then in your widget that is put inside the map children, do FlutterMapState.maybeOf(context)...

I re-implemented the eventStream in the mapcontroller, however I might revert that change later. I did it exclusively for the "map_controller.dart" example page due to how it handles state. But...

Alright I am happy with where this PR is and am happy to merge. I will work on migrating plugins over the next day or two. Still need to write...

Opacity is a slow widget to render and might be the cause of your performance issues. However a solution to preload tiles (from the server) would be convenient. Joining this...

Hi, I would like to post some of my own experience here with displaying a lot of Tiles. My app will typically display 48 tiles per view port, and has...

I have been working on rewriting the state management and now have flutter_map correctly initializing the map variables (other than buildconstraints on initState and the first build correctly gets constraints...

yeah I left the print in on accident. it's removed now. I will mark the pr as closing.

#1333 using setState should now build all children correctly and may fix this issue as long as you setState the entire map when switching which looks like what you are...