Discussions

Well, there are advantages and drawbacks either way. If all at one, you save time; but, allow pattern recognition to aid the user in clicking the appropriate squares. If seperately, it would be time consuming to flash the squares (especially when flashing each for 5 seconds, which seems like an exagerated amount of time to begin with); but, hides the pattern, making it more difficult to solve (however, limiting to 5 squares favors the user as well). With Simon Sez, each g

I will try to explain a little more clearly. Suppose you have an abstract class, AbstractClass. You cannot do this: <Code Omitted>This is what Hippo was trying to say. However, if you have a subclass of that class: <Code Omitted>then, you can create an object of type AbstractClass by instantiating the NonAbstractClass class: <Code Omitted>In fact, the World and Actor classes of greenfoot are abstract classes; yet, you can create worlds and actors no

oh.. obviously... thanks!

You may want to check out my scrolling tutorial to see how it all is accomplished.

Even I will try it.

Much thanks! :)

I think the easiest way would be to add the image when creating the world (so it is there before the run key is pressed). It starts with an invisible image, so you can't see it. Then it will itself give an image when it is running and will remove itself after 30 seconds: <Code Omitted>

It works!! see link of it... ---> FIRE AND ICE <----

Make sure that this code is in the act method and you do not remove the object from the world before executing this code (or prevent this code from executing if it was removed).

I found out the issue, it was referencing from multiple spots, so I created an if HP<0 then dead =1 and created if dead== statements to counter this issue.

As an alternative, you can utilize by BGMusic class to control the background music of your scenario. You can find it in my BGMusic Actor Class Demo scenario.

The constructor of an object is only executed once when the object is created. In your case, the 'Space()' method is executed once when your world is created. To check for key presses while the scenario is running, you need create the act method in your world class. This method will be called for the active world and all objects in that world, again and again. <Code Omitted>Using the 'getKey' method in a different context than writing text can create other issues though.

i have un commented it and it is still not working

Those two lines handle that: <Code Omitted> You changed the 2's to 30's in the first line, you have to use the same numbers in the second line.