Discussions

Seems to me, it would probably be a Java bug, if it is a bug at all. Though, Greenfoot is the one throwing the error and saying that a close parenthesis is needed.

When I was learning OOP (after first learning procedural programming) I found it helpful to think of instance methods as having a hidden first parameter, which was the target object, or 'this' in Java-speak. The parameter isn't declared but it is implicitly present in any instance method. Of course, you are able to access fields and methods of this parameter without qualifying them with an object reference (because 'this' becomes an implicit target reference for anything which can't otherwise be resolved). In my head, expressions such as: someObject.someMethod(3, 4); Became: so

@davmac That's what I tried to say :)

How about the 'fillPolygon()' method. Take the four corner points (let us say (0, 10), (0, 15), (600, 300), and (600, 305)) and break them up, listing the x's and y's seperately <Code Omitted>

I'll answer against your original post.

I solved it like Danpost proposed it and it really works well. Thank you!

Thanks, really helped :)

Make sure you have the latest version of Greenfoot. If you still have the problem after upgrading, please contact support@greenfoot.org, with the information listed on this page, and your code (preferably zip the whole scenario and send that).

It would be easier to spawn the rocket first, then spawn the rocks so that they are not near the rocket. This can still be achieved randomly with (in the world class constructor or a method it calls):

thank you =)

thanks :D I got it now.

Thanks for this ^^