Discussions

fixed the problem thank you anyway

thank you verry much, I have looking for this problem for almost three weeks. Your all verry good programmers. Thanks a lot again

Thanks! However, i decided to stick with the drawText() method which fixes this at the cost of having the timer look slightly out of place.

When the field and method were non-static, you were only changing the rotation of the new balloon which is never added into the world. So, all you saw was the original balloon with no changes to it. When you made them static, ALL red balloons take on the same turn value (which may not be the behavior you will want when more than one red balloon is in the world at any time).

<Code Omitted> For the jumping code, you can try to search here on the greenfoot website. There are a lot of discussions about it. Try to implement it and if it doesn't work like you want to it, show what you have tried, say what is happening and w

Thanks! What you said makes sense and I've fixed the problem now.

Please refer to the java trails, found here. The second section titled 'Trails Covering the Basics' is the place to start.

First off, 'new' should be a word by itself (not concatenated with 'Counter...'). The first line should be: <Code Omitted>This is provided you have something like the following line within the class (outside of any methods): <Code Omitted>Next, the Counter object does not (unless you added one or one is supplied that I am not aware of) a 'setFont' method. Maybe you mean to set the font of the image of the Counter object (the GreenfootImage object set to the Counter actor). There is a 'setFont' method that belongs to the Greenfoo

Thanks it worked! i didnt know you could use an act method in the world class.

It's like that: If you have more than one checkpoint (if you only want one, you can simply use a boolean which makes it a little bit easier): <Code Omitted>

Why do you need this Main class? Why don't you use the scene in the scene class itself? Not sure what your errors are, so I don't know if it could cause it, but if you don't want to manipulate the strings after the scenario started, you can use an array: <Code Omitted>

Then the easiest way would probably to add a separate class for it. It could look like this:

Oh, that's great. I didn't see the new version yet.