When you wrote "Fallin Angle" I thought this would be about bug. This idea doesn't sound good (and is hard to understand). Well... this is a joke, right?

He is a satirist.

You can upload your files only in the "Upload" section.

X: (((Sprite15.x+((Sprite14.x-Sprite15.x)* ('t')))+(((Sprite14.x+((Sprite.ImagePointX(5)-Sprite14.x)* ('t')))-(Sprite15.x+((Sprite14.x-Sprite15.x)* ('t'))))* ('t')))+((((Sprite14.x+((Sprite.ImagePointX(5)-Sprite14.x)* ('t')))+(((Sprite.ImagePointX(5)+((Sprite.ImagePointX(4)-Sprite.ImagePointX(5))* ('t')))-(Sprite14.x+((Sprite.ImagePointX(5)-Sprite14.x)* ('t'))))* ('t')))-((Sprite15.x+((Sprite14.x-Sprite15.x)* ('t')))+(((Sprite14.x+((Sprite.ImagePointX(5)-Sprite14.x)* ('t')))-(Sprite15.x+((Sprite14.x-Sprite15.x)* ('t'))))* ('t'))))* ('t')))

Y: (((Sprite15.y+((Sprite14.y-Sprite15.y)* ('t')))+(((Sprite14.y+((Sprite.ImagePointY(5)-Sprite14.y)* ('t')))-(Sprite15.y+((Sprite14.y-Sprite15.y)* ('t'))))* ('t')))+((((Sprite14.y+((Sprite.ImagePointY(5)-Sprite14.y)* ('t')))+(((Sprite.ImagePointY(5)+((Sprite.ImagePointY(4)-Sprite.ImagePointY(5))* ('t')))-(Sprite14.y+((Sprite.ImagePointY(5)-Sprite14.y)* ('t'))))* ('t')))-((Sprite15.y+((Sprite14.y-Sprite15.y)* ('t')))+(((Sprite14.y+((Sprite.ImagePointY(5)-Sprite14.y)* ('t')))-(Sprite15.y+((Sprite14.y-Sprite15.y)* ('t'))))* ('t'))))* ('t')))

Angle: angle( lerp(lerp(Sprite15.x, Sprite14.x, 't'),lerp(Sprite14.x, Sprite.ImagePointx(5),'t'),'t') , lerp(lerp(Sprite15.y, Sprite14.y, 't'),lerp(Sprite14.y, Sprite.ImagePointy(5),'t'),'t') ,   lerp(lerp(Sprite14.x, Sprite.ImagePointx(5), 't'),lerp(Sprite.ImagePointx(5), Sprite.ImagePointX(4),'t'),'t') , lerp(lerp(Sprite14.y, Sprite.ImagePointy(5), 't'),lerp(Sprite.ImagePointy(5), Sprite.ImagePointy(4),'t'),'t') )[/code:1r6s8h2j]
Hope you hadn't much debugging this stuff because it looks kinda messy. Sure it looks flawless, but I think you should pay more attention to documenting your code.

Use List object and load file into it. Retrieving 'n' line:

ListBox.LineText(n)[/code:1qwg8gn4]

More details:

http://www.teslakite.com/freemp3s/e/paprika/

I don't quite understand, but of two options:

mask

blit to canvas, erase

The first sounds faster because it doesn't modify canvas on every render.

Set Private Variable ('cointotal') for other object (for example Text Object, but not Coin). Increment it when collision with coin (instead of Coin: add 1 to cointotal, you should make Text: add 1 to cointotal).

Second test: Add TimeDelta vs Creation Time.

Goal: the most efficent way to access every object's "Age".

Methods:

Add TimeDelta always add TimeDelta to ('time'). Retrieving "age": Object('time')

Set Creation Time sets ('creation') at Start Of Layout. Retrieving "age": Timer - Object('creation')

First method does:

always add to PV (nobjects) times

always retrieve PV (nobjects * n) times

Second method does:

always retrieve PV and do subtraction (nobjects * n) times

In this CAP you can see multiplied events. These are simple operations for accessing "age" data. If you run this now, you'll see that "Creation Time" works better. If you add some of these multiplied events for both methods, you'll see that "Creation Time" loses its advantage, and it becomes worse method for more than 8 retrieves of "age" data.

Still there's nothing to worry since this operations consumes very little amount of processing power.

I've made an performance tests for intensive Private Variable modifying.

http://www.scirra.com/phpBB3/viewtopic.php?f=16&t=1768

I'll research "onCreate -> set to timer" method to compare which one is faster and under what circumstances.

Edit:

Added (in thread above).

In this CAP there's measured speed of every frame with 100000 outside layout in two modes:

no actions on objects

increment every object's PV

IMO foreach-ing works fast enough. Enjoy ^^.

Managing object's age can be done by one event (PV "age" -> add to value -> timedelta). ActionsConditionsExpressions shouldn't be filled with unnecessary entries.

OKey I just got easily offended. Sorry ^^.