-
Notifications
You must be signed in to change notification settings - Fork 504
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
Single reusable map instance #245
Comments
Would be great to get any update on this issue. How is this solved in Android and iOS Mapbox SDK? Can we reuse any approach? |
@AAverin Two potential hurdles I can think of right now: some users may want to instantiate more than one map at the same time, so we'd have to always keep one map instance around and be able to instantiate more. But also other users expect the memory to be released when the map isn't shown anymore, so making the map reusable would have to be configurable somehow. |
I am now struggling with this exactly. |
This, indeed, needs to be configurable somehow, because different users will have different needs. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Having many places where map can be displayed, it's very expensive to create new instance every time.
Is there some way in library of Flutter in general to somehow have single map instance that would be lazy initialized and later reused everywhere, just calling
onMapCreated()
callback when it's displayed?The text was updated successfully, but these errors were encountered: