feat!: add interactive Polygon
s, rework Polyline
hitTest
result, and deprecate/disable auto application of TransulcentPointer
#1822
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.
Added interactive
Polygon
sResolves #385. Requires #1800 to be merged first.
This uses a similar format as to
Polyline
interactivity.Reworked
PolylinePainter.hitTest
outputsHelps to fix #1740.
hitNotifier
hitValue
shitTest
internal output no longer depends on state ofhitNotifier
, to improve definitity without below...Deprecated
MapOptions.applyPointerTranslucencyToLayers
& changed default tofalse
, and removed usageTransulcentPointer.translucent
propertyFixes #1740.
MapOptions.applyPointerTranslucencyToLayers
causesPositioned
wrappers to fail #1740 was caused because disabling it did not unwrap children, it just used thetranslucent
propertyTranslucentPointer
itself has been retained as it is a useful resource to further customize hit testing behaviour, andCircleLayer
andOverlayImageLayer
still have no hit testing provision