You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If any reader has time, please help with getting Sprite and related classes thoroughly annotated
I can proof-read any PRs which make doc changes, so don't worry about imperfect doc
Otherwise, I'll give sprites a second look after the physics engine typing & doc PR
A Unified Physics Engine Type Probably Needs to Wait
As to the engine type / Protocol, here are my current thoughts after starting on #1981:
There seems to be a repeated pattern of inlined expansion into a list of SpriteLists + properties for checking collision
Abstracting some of that collision checking may clean up code at the price of execution
3.It's worth reconsidering Scene's layers and structuring and how it interacts with physics engine objects, but probably after 3.0
I haven't looked at the pymunk engine in months, so I I'm not yet sure about what a physics engine Protocol type should look like
Enhancement request:
arcade.Sprite.draw
andarcade.Sprite.register_physic_engine
have unannotated arguments (AKA Unknown) as well asarcade.SpriteList.draw
What should be added/changed?
Add type hints for the mentioned above members.
What would it help with?
It'll help users with development and understanding the actual valid type of arguments.
The text was updated successfully, but these errors were encountered: