Discussions

thx again sir

At line 118, insert the following: <Code Omitted>

wow, thx sir

Anywhere in the class not in a sub-block (method or constructor).

You could: <Code Omitted>or begin line 2 with: <Code Omitted>or, more simply: <Code Omitted>

Oh, you are saying that your scenario is running at a very slow frame rate. Run at normal speed, use a int timer to regulate moving and track direction input with another int field.

The 2nd word here says it all. Use: getWorld().getObjectsAt( ... )

I put it in the Greenfoot scenario the progress bars stop before the end while on the IDE they go to the end

turnTowards(int, int) cannot return something, because what should it? There are multiple things imaginable here. For example, which is what I think you thought of, return weather the object was looking at that location before anyways. But it could also return the angle in degrees it has rotated to face that object, or the new rotation after turned towards that location, or weather the locaiton given was actually valid to look at and not the objects location itself, or... You see, it really did not make any sence if you could convert void methods so that they return a value. If you want that

Okay:

Collision checking should come AFTER any change in position (or rotation) -- that is, any change not dictated by collision to begin with. There are two actions that should be performed when a collision occurs: moving (or rotating) off the object collided with and turning. The first of these is often missed by young coders.

In act method of Space class, you can use: <Code Omitted> Thank you Dan, that was the code I was missing. I should also mention, my professor also said that we were not allowed to modify the act method, so I replaced line 100 of the Asteroid class with the if statement you posted. It looks like this:

You will need to have the Instructions object retain the message for later use (add a String field and assign message to it) and then add a setColor method to the class that acquires a color (via parameter argument) and creates and sets an appropriately colored new image.

To stop a sound, you need a reference to it. After you changed to the new world in line 34 of the Title_Screen class, you won’t have any further chance to get a reference to the sound object from the newly created world, so it will run forever. A few alternatives you could go for: 1) stop the sound before changing the world 2) pass a reference when you create the new world 3) make the sound a class variable (static) instead of an object variable to access it from anywhere more easily