Discussions

Break the 'menu' down into simple parts that you can work with. For example, a menu has the following: (a) a background -- with possible texts and/or images; and (b) buttons -- actors that perform specific functions when clicked The menu background can be a world canvas or it can be an actor that is added behind the buttons. I have found that it is easiest the create a separate world for the menus. Having a separate world for the menu keeps it separate from your main world (no need to track objects that need removed due to the menu) and it keeps your main world from running while the

Insufficient data to ascertain. You need to show the block of code that the block given above is enclosed within or, if the block given is the complete code for a method, the block of code that contains the call to this method.

thanks so much danpost, really appreciate the help

IT WORKS! Thanks danpost.

I think you need to review the methods provided in the Greenfoot class documentation and choose a more appropriate method (other than 'isKeyDown').

I do not see any attempt at coding any collision. What have your tried? Things I have noticed: * class names should begin with uppercase characters (by convention) * method names should begin with lowercase characters (by convention) * the setting of the images for your cat, as coded, need to be read from file to create the image and then set every act method the cat moves; this is far from efficient and may cause lag; it would be far better to hold the images in fields and set the cat to the appropriate image only when a change in direction is detected. This means you would need three

Nevermind, I fixed it. I was supposed to check whether rotationDiff was greater than 0, not less than 180. Thanks for all the help guys! :D

Thanks Hippo, that did the trick :)

To call a method that's in the same class, you write the name of the method followed by parentheses containing the parameter values, if any. As 'updateCoords' doesn't have any parameters you can leave the parentheses empty in this case. If you don't understand something I've said, then please ask about it specifically. Writing a method call is so fundamental that you need to learn to do it yourself, so I'm not going to write it for you.

Just like the exception message says, you are calling a method (getOneIntersectingObject) which relies on the actor being in the world, but the actor (Crosser) has been removed from the world. You need to avoid calling getOneIntersectingObject after the actor removes itself from the world.

Thanks guys, I'll have a crack at that.

Thanks guys, I ended up using a bit of code from a video tutorial in Mik's Blog. Where the actor detected when it was at the edge of the world (either left or right side) and then when that was true it turned 180. I originally planned to have two 'barriers' at either end which had the same image as the side of the background but this turned out to work just as well. Thanks again for your time. :)

mobileash66, please use 'code' tags when posting code. (Click the link that says "Posting code? read this!" under the text entry area). Your code above looks wrong because it contains: <Code Omitted> ... which creates italic text.

thank you so much! I just realised my stupid mistake