Discussions

See here.

getWorld returns the world that the actor that the code is running from is currently in, I don't think you can get any other world, so the addObject will add it to the same world. (Not arguing with danpost just saying it in my own words)

Switch lines 44 and 45. You need the actor in the world when you call the 'lovit1' method.

thank youuu

You're welcome. Good luck ;)

Not unless the field ('length', in your case) is of type double or float (not int), or your unit of measure for 'length' is changed (instead of units, you assigned -- virtually --, say, 1/100th of a unit as the new unit).

Please show the code used to declare and fill the array and explain, in detail, what each part in the array is for (what the positions in the array represents and all values within the array). Then show the code for the 'for' loop that you have tried. If there are any unknowns within the codes given, explain what they represent.

Any variables that need to be maintained through multiple act cycles must be declared outside of any methods. That means lines 24 through 29 and what you have inside the 'Info' method (line 15). You can remove the 'pause' method as the timer will take care of that part. Instead of 'Info' as the name of the field that determines what needs done, I would use something more meaningful -- like 'step'. You can declare constants (outside of any method) to help in what step is what. For example:

Is there a way that I could have found the above link (here) on my own, because I have never saw it before until now and it would have helped me (I'm also wondering if there are other things there that I haven't seen).

The code that you would use to make the screen shake is basically the same as what you would use to make the world a scrolling world. The only differences are (1) the scrolling is limited to very short distances (vertically and/or horizontally); (2) what condition(s) are used for scrolling; and (3) the behavior of the scrolling. The third difference is really a result of the second one. Shaking the world is now included in my Scrolling Tutorial scenario and is demonstrated in my Scroll

Yeah i manged to noticed that like after i posted this :D However it worked thanks !!

I see. Many thanks for your input !

Let's say you have one class Card. And each different card is represented by a different 'type' value. For 5 cards, these values would be 0-4. If you press a card with type 3 and then one with type 2, it will add a certain number of points. The next card's previous is 2 then. The array could look like this:

The problem is not the amount of storage memory that is being taken up by the image files -- it is the amount of working memory for the project. You are probably creating all the images at the beginning and keeping them as GreenfootImages throughout the running of the project. I will throw around a couple of ideas. Consider creating them (the images) only when needed and not keeping references to them once their on-screen time is done. Using an array in your world class to contain all the necessary data on the states and using a single State object with changeable data would also help. Yo