Discussions

Okay so far i have <Code Omitted> which complies fine but doesn't actually delete the last minim created and I don't really know what i'm doing wrong

I do not understand what you mean. I do not see 'setDirection' nor 'atWorldEdge' in that list. Also, the 'move' method inherited has one int parameter and you are trying to call one without any parameters; so, the one you are calling is non-existent.

This should be categorized under 'Other', not 'Programming'. However, the answer is yes. My Clock/StockWatch/Timer scenario uses different worlds to run the different applications. This show the ability of both the choice making and of multiple projects in one. To show the versatility of greenfoot -- how about two games in one. Check out my PIP Actor Class scenario (not that you would want something like that).

First create a subclass of Actor to display the message; then give it the behavior (using the act method) to remove itself upon "whatever" key press.

oky thank you so much im new to green foot so my methods be out of whack. i have changed the 'if' statements and also the '17' and it helped tremendously.

You must be adding your actors into the world manually. They will not reappear when you reset unless you 'Save the World' after adding them. You cannot 'Save the World' once any act cycles have been executed; so, do this immediately after you have placed all your actors where you want them.

If you are going to assign 'card2' with an object, then there are several ways to go about it. One is passing the Card2 object to the Card constructor; one is finding the Card2 object when the Card object is placed into the world; and, another is using a method call to set a Card2 object to the field. The first and third ways are quite similar, in that they use parameters to the methods to pass the Card2 object to the "new" Card object. The second way, uses brute force to find the Card2 object in the world to get the object to be referenced in the field. Summary of the first and third ways

An easier way for the temporary message is to subclass the Message class with a TempMessage class with the timer int field and an act method to run the timer and remove itself when the timer is exhausted. That would keep the code cleaner in the class above and well as clean timer code. <Code Omitted>Then, to adjust the code Super_Hippo

You referred to the action "remove objects" and the location "bottom of my screen". For the first, you need to find the correct method (which should not be too difficult; although you may want to ask yourself "what am I trying to remove the object from?"). For the second, ask yourself "how do I know when a location is at the bottom edge of the screen?". The answers are (1) the world; and (2) when the y-coordinate of the location is equal to one less than the height of the world. Hopefully, that will lead you along the correct path to the solution.

Thank you very much, it worked :D

thanks danpost

Thank you very much.

You can limit the number of balls in the world by adding an if condition to the spawning of new balls (if the number of balls in the world is less than 4, or 5). As far as there being another way to add new balls into the world when one reaches a world edge, not really. @LordLuhar * the int field 'i' would be unique to each ball, so each ball will then know how many other balls that it has spawned; * 'Public' in line 3 should be 'public', starting with a lowercase 'p' (same on line 7); * 'class' in line 7 should be 'void' (there is no value returned from the method); * method names s

Super_Hippo, thank you!

One alternative (though not necessarily the simplest) is to move the check for both conditions to the top: <Code Omitted> Better would be to split the left/right and jump handling, essentially so that "left"/"right" both move and change the direction the player is facing, and "up" jumps in the direction they are facing.