Discussions

Nevermind, I fixed the issue by using a for loop:

do you know where i can find that code

For the above class: See methods at lines 154 and 157. To up speed by one:, use: <Code Omitted>or set it to any value (here, 3): <Code Omitted> However, I suggest you use the Scroller class linked to the demo and support class scenario discussed in your previous discussion. It is, in itself, a complete, re-usable support class that can be used for every type of camera movement. Also, it requires no modifications to your Actor subclass codes (even if actor is the one the camera follows).

Error output should always have the form <Code Omitted>This is supposedly help you identifying the error. The top location line tells you the exact location where the exception occurred. It should be highlighted as a link and you can click on it which will redirect you to that place in your code. Common exceptions are: NullPointerException - trying to access a method of field from a null value ArrayIndexOutOfBoundsException - Trying to get an element from an

Creating animations is very difficult in Greenfoot because you have to do all scaling, drawing and updating manually. But for a simple button you could use something like this: <Code Omitted>If you need more than one button you m

Thank you so much for this, really appreciate it.

Please provide full Boomerang class codes. Also, please provide full Items class codes. As well, please provide a little insight as to when a boomerang is to be created. If an actor type throws it, specify which type a how that actor plays a role in your scenario.

I've worked on a Tower class now, and I put this code in the determiner function, and it seems to be working well: Pie is the enemy class I talked about earlier.

Thanks again

Got it! Thanks

That is because an element is not trying to be extracted from a list without any elements. A test is done to the list to ensure an element exists in the list before extracting the element.

The use of "this." seems a bit ... off. Each usage is on a method that is located in the World class, which is the "super" of this class. More appropriate would be to use "super." instead. However. the methods are not over-shadowed by methods with the same names in the MyWorld class, so ... that is why it still works. Greenfoot does not force the use of a subject for method calls. As such, I suggest just dropping all the "this."s from the class. Next, you can remove all objects from the world in one simple call by using "Actor..class" instead of calling out all the different typ

Here is a simplified version of your class: