Discussions

If you are using the newest Greenfoot version, then there is greenfoot.Color which replaces java.awt.Color. Anyways, I didn't only write this last line.

You just need to add the two methods: <Code Omitted>into the two subclasses (SavingAccount and CheckingAccount) with their appropriate codes (as per lines 27 and 28 of the Account class).

What you meant here was -- why not: <Code Omitted>Probably because of what the example portrays. Oftentimes, beginners try to assign the variable with something like the following incorrect code as the second stage: <Code Omitted>This does not set the new image to the field declared in stage one; but, instead creates a new variable and assigns the

Thank you so much! I tried the squiggly bracket and it worked. I appreciate your help.

Change: <Code Omitted>to <Code Omitted>and put <Code Omitted>in the constructor block that starts with 'public Lebensanzeige(Spieler1 s1){'.

i love you man thank you !!!!!!!!!!

You could also write it like this in the act method: <Code Omitted>and add the following method to the World subclass:

My Animation class can be made to run exactly one cycle of images just by setting a cycle count field. My GifImage vs Animation scenario contains both the Animation class as well as the GifImage class provided by greenfoot and shows the various differences between them. Also, my Animation Support Class scenario demos a single cycle usage. Well, I see that it does 6 cycles (which looks like one visually) because the pattern repeats 6 times.

After moving, check the changed coordinate by comparing it to whatever limit you set for the direction moved. If passed the limit, move the actor back to that limit (using 'setLocation'). For example, to limit movement to the right so the actor does not go off the visible world: <Code Omitted>You can change the '1's to a larger value to put more of the actor in the world. Using 'getImage().getWidth()/2' instead of the '1's will place the actor at the edge and totally visible (no part

thank you very much. I now have an own idea:

Thanks! It works now.

Show the act method of the class.

First thing is that it is not the class that has coordinates -- it is the objects of the class (that are subclasses of Actor) that have coordinates. That being said, you need to acquire a reference to the Om object in your world from within the Rac class. If there is always an Om object in the world, you can use: <Code Omitted>to acquire that reference (in 'om'). However, if it may be possible that there is no Om object in the world, you will need to preface that with the following: