Discussions

I have seen this in the case that I leave the mouse cursor over the "run" button after clicking it. The button changes to pause, and when this happens, a tooltip appears for the pause button. At this exact moment the scenario stops responding to keypresses. The good news is that this only seems to happen once, and also that it looks like it's been fixed in our development codebase (but not in Greenfoot 2.4.1 unfortunately).

Ok, received, and yes, it was an obscure bug in the Greenfoot collision-checking code (it can only trigger when there is only a single actor in the world). Thanks. It will be fixed in the next release.

You need to extract the downloaded zip file somewhere. You could extract it to your hard drive, but in that case it's better to use the proper Windows installer instead.

It's saying that the heap is exhausted. The heap is used to store objects and arrays. In Greenfoot, the most common cause of this is that you have a too-large image in your scenario's images folder. Another way of causing it is by having a "memory leak" in your program, where you continuously create more objects and do not reclaim old objects. In Java programs this isn't so common, since the "garbage collection" process

Your ship has a rotation of zero, which makes it move left and right with 'move(-10);' and 'move(10);'. By setting the rotation of the bullet to that of the ship, the bullets will also move left and right when using the 'move' method. If you want to use the 'move' method to move an object upward, that object must have a rotation of '270'. This may or may not have the unfortunate result in having your bullets flying sideways depending on the image used for them. There are several ways to avoid this. Re-post if help is needed in this regard.

What method is the code from line 16 down in? Look like an undeclared block of code to me. Then, what two objects do you want removed at once?

What are the dimensions of the image that is set to the line object?

The SmoothMover class probably has a 'public void move(double distance)' method, or something like that. If so, you can just do: <Code Omitted>

In what way is the difficulty to increase? Show what you have tried?

For the value of 'x' in line 34, you will need to add '2' instead of '1' or case 21 will never be used and nothing will show for case 1. As far as the fields in the Background class, lines 12 and 13 can be removed (not used anymore). Line 11 can also be removed; but, line 34 will need to be adjusted to this: <Code Omitted>As I do not know what 'var' (line 14) is for, I cannot say whether you need it or not.

There are multiple discussion threads dealing exactly with this issue. Usually, it is the case that they have something like this; <Code Omitted>and do not realize that they can split the line up to this: <Code Omitted>By doing this, they can then proceed to call methods on the new game over world. For example:

Show what you have tried.

I fixed it ! Thank you

Thanks :)

This should be a continuation of your other discussion post -- not a new one.