-
-
Notifications
You must be signed in to change notification settings - Fork 860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Marker/Map rebuild causes marker to lose state #256
Comments
Can you include a small example that demonstrates the issue? |
Flutter keys do not keep State if no StatefulWidget is present with the same key so when the Marker is outside of the visible boundaries the builder will not be called and the associated StatefulWidget will not be rebuilt. |
A small example of what happens can be found in this gist |
@GregorySech Hi Gregory, I assume you and @johnpryan are very busy lately. I would like to know if there are any work for version 0.8? Actually since using this awesome package for my app, I would indeed like to know if you have plans for maintaining this package in the future? Seems a long way for google_maps_flutter to support marker widgets hence making this package very important and unique. I haven't seen a new version in the last 3 months and would be glad to get feedback from you guys. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
I am animating some of the markers' opacity making them visible and invisible. Let's say I make one marker invisible. I can pan/zoom map and the marker stays invisible as expected as long as it is in screen bounds. This works well even if other markers leave the screen hence triggering markers to be rebuilt. But when the invisible marker goes out of screen and back in again, it is built as visible. I tried something like this using Keys hoping it would solve this situation. I am in need of help since I can not totally grasp the inner workings of Flutter_map @johnpryan @RaimundWege
The text was updated successfully, but these errors were encountered: