Discussions

What ?? I indicated that you created one. Creating it does not put it in your world, however. You need to add that (created) TextArea object into the world to make it show.

What steps were required when taking the object? (show code)

Using turn(180) instead of setRotation(180) will make it repeat. To go 2 cells instead of 1 may require an int counter. Being you only want it to move 2 cells, a boolean may work just as well. Even a simple: <Code Omitted>may even work (without a field at all).

nvm i figured it out thanks

I do not see where any EndScreen world is being created.

thx a lot

Each time the MusicUp button is clicked, a new instance of Music is created. The Music class is def not designed in any type of "singleton" pattern.

Lines 4 and 5 of your new code does not make use of the last two methods I had suggested you use.

From what I can tell from what was given, getRandomNumber appears to be an undefined variable. Also, the expression for the if condition looks to be an int value, not a boolean one (which is required for a condition). Another problem is the previous line which is just a loose int value -- it is like coding a line like: <Code Omitted>or <Code Omitted>(both uncommented) which is really equivalent to <Code Omitted>a non-operative statement. Create a local int variable and assign the random value to it:

Basically, you are wanting to make two buttons, which are, in essence, text display actors that clicks are detected on. Please refer to my Value Display Tutorial scenario.

Yes -- and no. The setPaintOrder method can be used to have ALL of one type object showing over ALL of another type. Otherwise, there is no documented way of doing it. Currently, however, objects more recently added into the world will show over those objects already in the world. This means you can take an actor and remove and re-add it into the world to have it show above another actor.

With what you have given, I cannot see any reason for what you say is happening. The only strange thing I see (which I cannot expect to be related to your issue) is the exclamation mark inside the filename of the image -- and that may be fine, as is.

Remove the counter and add a boolean to track the state of the "space" key. Check for a change in the state of the key by comparing current state to previous state (held by field). When a change is detected, update the field and check its new value to determine when to shoot.