Keep improving event docs #1695
Merged
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
Added a new using directive for LiveChartsCore.Kernel.Drawing. Revised descriptions for TooltipFindingStrategy enum members to clarify comparison logic involving HoverArea in X and Y axes. Introduced a new enum member ExactMatch to check if the pointer is inside the drawn shape.
…sest Updated comments for CompareAllTakeClosest, CompareOnlyXTakeClosest, and CompareOnlyYTakeClosest to clarify behavior on overlap. Added new enum value ExactMatchTakeClosest with explanation of its functionality.
Adds ExactMatchTakeClosest to the series that need it.
The code now assigns the TooltipFindingStrategy to a variable and checks if it is set to Automatic. If so, it calls VisibleSeries.GetTooltipFindingStrategy() to determine the appropriate strategy. This change enhances the flexibility and adaptability of the tooltip behavior.
This returns a new instance... is not a cast actually...
This reverts commit ace07e8.
Rename to findingstrategy
also renames on views TooltipsFindingStrategy to FindingStrategy
…cesibility Improve chart methods accessibility
This was for the events branch :(
The `TooltipFindingStrategy` property has been renamed to `FindingStrategy` throughout the documentation. The description of the `FindingStrategy` property has been updated to reflect its role in determining the hover area planes (X or Y) that a chart will use to trigger the `HoverArea` instances. The list of available options for the `FindingStrategy` property has been updated and expanded to include `CompareAll`, `CompareOnlyY`, `ExactMatch`, `CompareAllTakeClosest`, `CompareOnlyXTakeClosest`, `CompareOnlyYTakeClosest`, `ExactMatchTakeClosest`, and `Automatic` (default). Updated images and descriptions for each `FindingStrategy` option have been added. Code examples in different frameworks (XAML, Blazor, WinForms) have been updated to use the new `FindingStrategy` property name. The section on customizing the `FindingStrategy` has been updated to reflect the new property name and includes a link to the updated documentation. Minor formatting and grammatical corrections have been made for clarity and consistency.
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.
No description provided.