Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add convenience layer for IntersectionQuery #20

Open
thelonious opened this issue Nov 21, 2017 · 1 comment
Open

Add convenience layer for IntersectionQuery #20

thelonious opened this issue Nov 21, 2017 · 1 comment

Comments

@thelonious
Copy link
Owner

Right now, you can use the intersection API 3 ways:

  1. Direct call to intersection method passing in essentially scalar values
  2. Via the Shapes API which still uses scalar values, but it creates intermediate objects for each support shape. These are then used by a single method in the intersection API to determine which low-level method to call
  3. Via the Affine Shapes API which is just like the Shapes API, but it lets you use Point2D, Vector2D, etc. in place of scalar values. This is for people who don't mind using those classes.

IntersectionQuery has been introduced recently and right now it has the equivalent of the intersection api's low-level interface. Using either of the Shapes API, we should be able to introduce a simple IntersectionQuery.contains(point, shape) method.

@brettz9
Copy link
Contributor

brettz9 commented Apr 28, 2019

A contains method (if not containsOrIntersects) sounds very useful!

@brettz9 brettz9 mentioned this issue May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants