feat: add dblClickSpeed
init config (#1710)
#1736
Merged
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.
🤔 This is a ...
🔗 Related issue link
💡 Background and solution
Previously, double-click detection was implemented internally with a hard-coded 200ms threshold.
Now, users are allowed to configure a
dblClickSpeed
initialization parameter to customize the speed of determining whether two consecutive clicks trigger a double-click event:Please refer to the documentation for double click events: https://g-next.antv.vision/api/event/faq#%E9%BC%A0%E6%A0%87%E5%8F%8C%E5%87%BB%E4%BA%8B%E4%BB%B6
📝 Changelog
dblClickSpeed
init config (#1710)dblClickSpeed
初始化配置 (#1710)☑️ Self Check before Merge