feat(renderer): Implement getPieceIndexAt Method
#53
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.
Summary:
Introduces a new public method,
getPieceIndexAt(x, y), to theRenderer. This method provides a direct way to get a piece's index from canvas coordinates, enabling developers to build custom interactions like tooltips or hover effects without being tied to the built-in event system. It effectively serves as the public-facing reverse operation togetPieceCoordinates, enhancing the library's flexibility.Changes:
Added Public Method:
renderer.getPieceIndexAt(x, y)to retrieve a piece index from canvas coordinates. This method leverages the internal hitmap for efficient lookups, returning-1if no piece is found.API Documentation:
getPieceIndexAtmethod inAPI.md, including a description, parameter details, and a clear usage example.