Discussions

thank you

sorted it now but thanks

thanks

ok thanks. its 365KB well under :)

The 'else' is not neccessary, as any code following the snippet I provided will execute if 'not sleeping'.

yaaaaaaay! finally worked properly :D thanks for your help guys Craig

@nccb that makes lots of sense.

It's possible, yes. I don't really know the context, so I can't say just how to do it, though. You could probably put in some code in the "eaters". When the "eaters" eat, they check to make sure that they are not in a safe zone. You could have the safe zone be its own type of Actor. Choose an image to bound the safe zone. If you do, than the "eaters" could just check <Code Omitted>Since the image is always square shaped, having a round safe zone would take some tinkering.

Ok.. thanks!

thanks! that definitely helped!! im going to go through the code and fix it up with better naming conventions.

If they are different classes, you can use the setPaintOrder method of the world: see the docs locally or at http://www.greenfoot.org/files/javadoc/greenfoot/World.html. If they are the same class, there's no mechanism for changing the paint order.

Unfortunately, OpenNI, the middleware we are using, doesn't support control of the camera. So I'm afraid moving the camera is the best solution. I usually find that since you have to be a little way back from the camera anyway, putting it on a high table, or on top of the computer case on the table, usually works.

Not sure what you mean by the 'engine', but if you're talking about the scenario itself, it can do any prep work it wants during the act cycle - either at the end or at the beginning. The thread sleeps only if all the actors have finished acting. Greenfoot is meant for beginners, and multi-threading is an advanced topic. There