Enhancements for splayed cluster manipulation #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mount. Modify the DisplacedMarker´s marker once a ModifyMarkerEvent is fired.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @rorystephenson,
based on the current working state of the v5 branch I have added two modifications which allow the developer to customize the splayed cluster behavior regarding the two following points:
In the current implementation the markers are overlapping if the splayed cluster contains too many markers.
The change introduces parameter distanceIncrement for SpreadClusterSplayDelegate which can enlarge the radius by multiplying it with the amount of contained markers.
Screen_recording_20240228_094813.mp4
Screen_recording_20240228_095035.mp4
In the current implementation markers within a splayed cluster cannot be modified. Only after applying another re-creation the changes for the marker itself will be visible.
The change introduces a mechnism which will dive into the splayed cluster and replaces the marker of the DisplacedMarker so that the modification is directly visible in the map.
Screen_recording_20240228_094923.mp4
I would be very happy if you could pull those changes to the next version of flutter_map_supercluster