To determine whether the mouse landed on the overlay or the feature w… #15476
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
…hen it is moved over a certain area.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
In a scenario where nodes and overlays exist in the same layer, and the coordinates of the features and overlays are nearly identical, the ol/Interaction/Select API may have difficulty recognizing if the mouse is over the overlay and the feature, making precise selection challenging. A typical use case in this scenario is on a map where there are multiple connected line segments, and each connection point (the two endpoints of a line segment) may have overlays as icons. The line segments may intersect these overlays. Therefore, I have provided a method to identify and set specific targets for selection in the filter of the Select selector.