fix click/hover on lines: use minDistance and optimize functions #157
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.
Somehow with all the newly merged PR's the click/hover function for Lines returns worse results.
That is because currently only the last found feature is returned.
I changed that and included a new variable
minDistance
, so that the feature with the smallest distance will be returned.Some optimizations for
tryClick
andtryHover
for Lines:checkClick
,checkHover
functions outside the loops.chosenWeightFn
outside the second for-loop, to not repeatedly check the data type.Set
instead ofArray
foroldHoveredFeatures
andnewHoveredFeatures