-
-
Notifications
You must be signed in to change notification settings - Fork 877
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
LateInitializationError with polygonCulling in PolygonLayerOptions - with example #1037
Comments
Same issue here.
Can't it be assumed that if the bbox is already calculated, it probably didn't change? |
Any difference if poly or polylines isn't final ? |
Not sure I understand your comment.
There is no way to reset it. |
The interesting thing is that there isn't even a way to check if it is initialized or not? Can that be?
It throws me an exception: LateInitializationError: Field 'boundingBox' has not been initialized. |
Yeah it does make a difference. This is my fix: Also, since my bboxes are calculated elsewhere I parameterized it to avoid the extra overhead. EDIT: |
This is working for me without using late modifier |
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 want to inform you that the problem is still relevant with polylines |
Here's an example that reproduces the error and a proposed fix: jithware@dd418f8 |
This Bug still exists? |
What exact error and what exact version of flutter_map are you using ? |
Same as #974 and #931 but opening as a new issue since those were closed.
Upgrading FlutterMap from very old version I am encountering
LateInitializationError: Field 'boundingBox' has already been initialized
whenpolygonCulling=true
.The problem crops up when I hold reference to
polygonOpts
in a stateful widget. This seems reasonable to me as rebuilding polygonOpts would be unnecessary.Example
polygons: [poly],
for the inline Polygon instance and exceptions won't be thrown.The text was updated successfully, but these errors were encountered: