What it does
SpritePhysicsAngularVelocity takes iSpriteIndex (an integer), and answers a float. That is the first of 2 forms. iSpriteIndex is the id of a Sprite object, the one CreateSprite returned: it is how the call knows what to act on.
Syntax
1
SpritePhysicsAngularVelocity(iSpriteIndex integer) → float2
SpritePhysicsAngularVelocity(iSpriteIndex integer, va float)Parameters
| Name | Type | In forms |
|---|---|---|
| iSpriteIndex | integer | all |
| va | float | 2 |
What each form returns
| 1 | SpritePhysicsAngularVelocity(sprite) | float |
| 2 | SpritePhysicsAngularVelocity(sprite, 1.0) | nothing |
Example · generated
Form 1, the command hands back the id
image = LoadImage("assets/sprite.png", 1)sprite = CreateSprite(image)DO Print(SpritePhysicsAngularVelocity(sprite)) Sync()LOOPForm 2, you choose the id yourself
image = LoadImage("assets/sprite.png", 1)sprite = CreateSprite(image)SpritePhysicsAngularVelocity(sprite, 1.0)DO Sync()LOOPLoadImage and CreateSprite are there to give the call something to act on; SpritePhysicsAngularVelocity is the line that matters. The DO … LOOP is not decoration: a classic BASIC program ends the moment it runs out of lines, and Sync() is what draws the frame.