Discussions

never mind. someone else explained it but thanks for your reply. I got sum is initialized to be 0. x = 2; x < 6 (true), sum = 0 + 2 = 2 x = 3; x < 6 (true) sum = 2 + 3 = 5 x = 4; x < 6 (true) sum = 5 + 4 = 9 x = 5; x < 6 (true) sum = 9 + 5 = 14 x = 6; x < 6 (false) The program terminated The last value of sum is 14 I didnt understand how to distribute the handy chart you provided but now I understand

This is an improper way of showing what you have tried. You need to show the actual code you tried. Please read the 'Posting code? read this!' link below the reply box before posting the actual code you tried.

ok thx

Thank you so much danpost what u said worked

Thank you, if works perfectly! I get an error at the end when the player dies, but I'll be able to fix that myself. Once again, thank you!

Gravity is just a continuous adding to the vertical velocity. That is, represent the vertical speed of your character with a field (instance variable) and add a constant (gravity) to it every act cycle (continuous adding). Do not forget to use the field when moving the actor vertically. Using the background color would be very tedious -- especially since there are already methods available in the Actor class to check for intersection with other objects. Create Actor subclasses for the objects that represent Ground or Platform (black); also, do the same for the Gate or Door (red)

I think you should read that API documentation more carefully: This method does nothing. It should be overridden in subclasses to implement an world's action. That gives you the answer to your question. Incidentally, the wording is almost the same as for the Actor's act method: The default implementation does nothing. This method should be overridden in subclasses to implement an actor's action. In other words, the act() method for the World and Actor subclasses works in exactly the same way. The only difference is that when you create an actor subclass, the class wil

I made a few changes and it now works perfectly. Thanks for the help, danpost and davmac.

You could add a boolean field and call it 'charging'. Use it to prevent boost, if charging, until recharged (when 'rechargemtr == 100', set 'charging' back to false). Set the 'charging' field to 'true' when 'rechargemtr == 0'. Only recharge ('rechargemtr++') when 'charging' is true). So, you would be doing the following two sets of steps at various places in your code:

Moving is not the only thing here that may cause a collision with a Wall object. Rotating the actor may also be a cause. Therefore rotation must also be negated if it causes a collision. The following may be closer to what is required:

Show the code you are using. Cannot fix unseen code. This not only means what you used by my suggestion, but also the 'setScore' method in your world class as well.

The refer to the positional offsets (the amount of movement) along the horizontal and vertical axes -- the change in value of the location coordinates for the given movement.

Work on one thing at a time. What have you tried as far as the children dropping garbage?