Implement visual geometry hit testing#21768
Open
emmauss wants to merge 4 commits into
Open
Conversation
|
You can test this PR using the following package version. |
This file contains hidden or 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
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.
What does the pull request do?
This PR introduces geometry-based hit testing, extending the existing point-based hit testing infrastructure to support testing against geometric shapes. This enables applications to query visuals intersecting arbitrary geometries (ellipses, custom paths, etc.) rather than just single points.
What is the current behavior?
Currently, hit testing infrastructure only supports point-based queries via
IInputElement.GetInputElementsAt(Point),Visual.GetVisualsAt(Point), and the renderer'sHitTest(Point)methods. Applications cannot efficiently query for all visuals intersecting a geometric region.What is the updated/expected behavior with this PR?
The PR adds parallel geometry-based APIs:
Geometry.FillContains(Geometry)method to test intersection between geometriesInputExtensionswith geometry overloads:GetInputElementsAt(geometry)andInputHitTest(geometry)VisualExtensionswith geometry overloads:GetVisualsAt(geometry)andGetVisualAt(geometry)IHitTestermethods:HitTest(Geometry)andHitTestFirst(Geometry)How was the solution implemented (if it's not obvious)?
The following api has been added
Checklist
Breaking changes
Interfaces were extended using default interface implementations. There shouldn't be any breaking changes.
Obsoletions / Deprecations
Fixed issues
Fixes #16549