Davide Tantillo 196df9c386 [haxe][starling] Replace bounds calculation with BoundsProvider system. Close #2915.
Replace direct bounds calculation with BoundsProvider interface for better
performance and correctness. This enables filters to work properly and makes it easier to get the correct bounds (SkeletonSprite.bounds).

BREAKING CHANGES:
- Removed getAnimationBounds() method. Replace it with the appropriate BoundsProvider implementation based on your use case, or create your own.
- hitTest() now uses the assigned BoundsProvider instead of direct calculation. For accurate hit testing, use CurrentPoseBoundsProvider and call calculateBounds() each frame or on click.

New features:
- Add BoundsProvider abstract class and AABBRectangleBoundsProvider, CurrentPoseBoundsProvider, SetupPoseBoundsProvider, SkinsAndAnimationBoundsProvider implementations
- SkeletonSprite constructor now accepts a third optional parameter for BoundsProvider. SetupPoseBoundsProvider is used by default.
- Added calculateBounds() to recalculate bounds on demand (useful with CurrentPoseBoundsProvider)
2025-10-08 17:49:59 +02:00
..