Discussions

There is a fill() method that requires no parameters. <Code Omitted>

I understand, you need both references to 'trailing' and 'leading' segments in each segment (except null for 'trailing' in last segment and null for 'leading' in first segment). Very good. I wrote a quick random movement snake program, nothing but the snake moving around the screen randomly; except that you can click on a segment and split the snake into separate snakes. Interesting :/

*make all your Actor-Subclasses go UP

winkleden - if you didn't tick the "publish source code" checkbox when you uploaded the scenario, then the source code didn't get uploaded and in that case there's no way you can open the scenario in Greenfoot.

What do you mean - do you mean the image, or the behaviour?

O... so that is how I can use private ... xD now I understand, thanx

aha... thanx, that will probably be the cause... thanx again yes... it works -.-

Hi, The object bench is effectively replaced by the world. Once you have an actor in the world, you can call methods on them in the same way as you can on objects in the object bench in BlueJ. The trade-off is that while you have to extend Actor, you can make the methods have more obvious effects (moving the actor in the world, or rotating or changing image) which can make the results a bit more obvious. So my advice if you want to use Greenfoot is to make your first classes Actors, but that way you get to call methods on them. I don't think we have any plans to add the object bench to

I know I did something akin to 3D display with my Earth/Eye scenario http://www.greenfoot.org/scenarios/990 but I don't know how applicable it would be. Probably the best bet would be to use something like http://lwjgl.org/ to interface directly with OpenGl to get fast 3D graphics, as eventually I think serious games need to graduate themselves past the more beginner oriented Greenfoot.

Users have the option to share the code, or not, when uploading a scenario to the Greenfoot site. If you see the big green "Open in Greenfoot" button to the right above the scenario, the source is open (available to other users), and the scenario can be downloaded by others.

Collision checking should probably be done within the Frog class, as the frog is the main object in the collision (the frog is always involved when a collision occurs). Also, it is the frog that has to be relocated, not the other objects. BTW, 'get eat' really does not say much. When talking about a method, it is best to describe it in detail (give info such as (1) when the method is called (2) what the method is supposed to do (or what information is returned (3) what class the method is in and, (4) any other information that may be helpful (like wh

Those are just backups of the source files. They are harmless.

Well, I was talking about "The Greenfoot Programmers' Manual". Before published in - http://www.greenfoot.org/doc/manual.html This manual still exist? Or this manual was updated and published in parts in http://www.greenfoot.org/doc/tut-2? Thanks