1. App Inventor Chapter 17 – Creating Animated Apps

2. From introduction: This chapter discusses methods for creating apps with simple animations - objects that move. You’ll learn the basics of creating two-dimensional games with App Inventor and become comfortable with image sprites and handling events like two objects colliding.

3. The illusion of animation On all display devices animation is achieved by providing a succession of still images or ‘frames’ with the ‘moving’ object(s) appearing in each frame slightly displaced from the previous frame. ‘Flipping’ through the images at a rate of about 12 fps or higher gives the illusion of the objects being animated. Most current display devices present frames at 30 fps in the US (25 fps in Europe). Interesting factoid: your local movie theater goes at only 24 fps!

4. App Inventor tools for animation In App Inventor you will place ‘Ball’ and ‘ImageSprite’ components in a ‘Canvas’ to achieve 2-D animation Start by adding a Canvas component to the Component Designer. Set its ‘Width’ to ‘Fill Parent’. Set ‘Height’ to something reasonable (leaving room at the bottom for other components) – say 300 pixels.

5. The Canvas coordinate system

6. Start with Canvas.PaintColor to choose a color. Example: Paint on Canvas with DrawLine & DrawCircle This colors a single pixel blue. Where on the screen does it do this? What controls the fact that is only one pixel?

7. Ball and ImageSprite components Besides painting pixels you can define and use Ball and ImageSprite components Ball and ImageSprite components can only ‘live’ somewhere on a Canvas component. A ‘Ball’ is one particular kind of ImageSprite. It is always round and you can only vary its size and color. ImageSprites are based on actual JPGs or PNGs or GIFs.

8. Using Timers to animate components This is a common way to do animation. Later, we’ll see how you can use a component’s.Speed and.Heading methods to control animation. In Component Designer, drag out a Clock component and set its TimerInterval property. A TimerInterval set to 1000 = 1 second; 500 = ½ a second, 100 = 1/10 th of a second, 10 = 1/100 th of a second, 1 = 1/1000 th of a second, or one millisecond. Drag out a Clock.Timer event in the Blocks editor. Whatever actions specify inside the Clock.Time will be performed at whatever TimerInterval you have set.

9. Creating Movement Example (moves ball horizontally across screen): Does the ball move to the left or to the right? What two settings control how fast the ball moves? What if you wanted to move the ball vertically instead of horizontally?

10. What’s the difference? Suppose we set a TimerInterval of 1000 and a MoveTo command of X+200 Then we set a TimerInterval of 100 and a MoveTo command of X+20 Which moves faster or slower? Which moves more smoothly?

11. What does this block do?

12. Collision detection and EdgeReached App Inventor uses high-level ‘algorithms’ to figure out when two ImageSprites might have collided with one another or when an ImageSprite encounters the edge of the screen. Good thing; otherwise you would have to come up with that logic yourself which ain’t easy to do!

13. What do these blocks of code do? This change made to correct an error in the book

14. Particular edges In the example, if the ball encountered any edge, the code sends it back to (1,1). There is a parameter that can distinguish among the edges – it takes the following values: North = 1 Northeast = 2 East = 3 Southeast = 4 South = -1 Southwest = -2 West = -3 Northwest = -4

15. CollidedWith and...

16. ... NoLongerCollidingWith

17. There may be a particular ‘Other’... This is a block that refers to a particular component as a whole, rather than specific properties of a component

18. Interactive Animation One technique: use a button-click to switch Timer.Enabled ‘On’ and ‘Off’ But this is just a ‘one-way’ switch. We need more sophisticated behavior. Take a look at this next slide....

19. More sophisticated button behavior...

20. Sprite animation without a clock timer (.Heading and.Speed) Take a look at this:

21. This code will control.Heading (How??)