Object Movement

The act() method for all objects is called in turn. So if you have two actors "a1" and a2" then: a1 acts, then a2 acts, then a1 acts again, then a2 acts again, and so on. It's honestly that simple. With the behaviour you've described, it sounds like it's something else in your code that's causing the smaller object to stop moving. How exactly does the larger object get requested to move?

This sounds a lot like the crab scenario :p You can always take a look in there and compare it to your code.

Thank you davmac, that explains it perfectly! My first actor's, a1, act() is lengthy, including multiple image swaps and directional changes with small wait times. I am new to programming and have decided to learn with Greenfoot. You hear all these ads about Windows machines being able to truly multi-tast so I wasn't sure if both acts were suppose to run simultaneously or if they ran in turn like you've described. Knowing they run in turn tells me it is my code and I'm trying to do too much at once. Also, thank you Duta, it is a lot like the crab scenario. In fact, the crab was my starting point and have grown from that foundation. Thank you to both of you!