Discussions

Thanks a lot azazeel, it worked!

Thank you so much danpost! This should be a big help for me.

You could try implementing my ImgScroll class. It is available through my Bee Quick (ImgScroll Demo) scenario. I believe it would be sufficient for your needs. Look over my demo to see how it is used (also look at what methods are available in the ImgScroll class). If you have any difficulties in implementing it into your project, please do not hesitate to continue this discussion thread.

My thoughts exactly. However, I can say that 'MoveandTurn' is never called and big problems exist with lines 32 through 34. Line 32 declares a 'World' variable (initialized as 'null') that line 34 tries to call 'removeObject' on (cannot call method on a 'null' reference); and line 3 declares an 'world' int type field that line 33 tries to assign a world object to.

Since you cannot use array, I suspect you would have the string packed like this: <Code Omitted> You can move the A to the End doing this: <Code Omitted> and you can Move the E to the front doing this <Code Omitted> This will work for strings of length 1 and greater. Using this you can probably figure out how to do the swap on the front of the list.

Once the current world is no longer active and there are no active references to it, it will automatically be flagged for garbage collection. Most, if not all, of that is done when you set the new world active (line 11).

Increasing the 'placeholder' field of your Ship object does not increase the 'NumberLasers' field in your SpaceBack object. Anyway, it is usually not a good idea to have two different fields hold the same information (one reason is because of the issue you are experiencing here). If each Ship object created is allowed to fire up to 4 lasers, then the field should be an instance field in the Ship class -- not in the world class. Also, as such, you would not have to acquire the value from the world.

Try typing Greenfoot.<space> You will get a lot of premade methods. There may be a stop sound method in there.

Greenfoot does not care about the indentation. You could get rid of the brackets if there is just 1 code underneath the if statement in this case. IF there is more than 1 you need the brackets. <Code Omitted>

I think the angle between the two actors would be as important as the distance. The angle would determine the shape of the shadow (angle and direction) and the distance and intensity of the light would determine the density of the shadow. Do not think of it as increasing or decreasing, but as what it would be like at any particular instance in time.

A major issue is the act method of the WallRect class. Once the 'player1' and 'player2' variables are set at lines 17 and 18, they are never reassigned values. So, if 'player1' is not null at line 19, then it will also (still) not be null at lines 29, 39 and 49 (and similar with the 'player2' variable). As a sidenote, changing the rotation of an object with a perfectly square uniform image at 90 degree increments would only be useful if you were using 'move(int)' to move the actor in the four cardinal directions. It appears what you are trying to do is to have the walls move constantly and

What class, method, and line is the castle supposed to be losing health on?