Discussions

Maybe you should consult this page of the java tutorials.

The fourth number is called the 'alpha' value. It is the value that is changed when you use 'setTransparency' on an image. The value you give in the 'setTransparency' call is what the alpha value is set to. Unfortunately, the name of the method is sort of the opposite of what it does (it should probably be called 'setOpaqueness'). That is, the lower the value given, the higher the actual transparency. At the high limit of the value, 255, the color (or image) is completely opaque (totally non-transparent). The lower the value set on the color, the fainter and less apparent the color beco

The five methods you mentioned above are all the Greenfoot class methods that deal with mouse input. The 'getMouseInfo' method does not deal with input; but, instead, provides a way to get more information about the mouse input (actor clicked, buttons pressed, click count and location of mouse).

The fix was changing the last 'getY' in the angleTo method of the Mover class to 'getX' and changing the last 'getX' in the distanceTo method to 'getY'. You do not have to add the 'getExactX' and 'getExactY' methods if you do not want to. The exactX and exactY fields have protected access from within the Mover class meaning that can be directly referred to in its subclasses. You should, however, change the 'getX()'s and 'getY()'s within the first statements of the act methods of your sub-classes of Mover (Mass1 and Mass2) to 'exactX' and 'exactY' (or 'getExactX()' and 'getExactY()' if you

It is the removal of line 12 that will help. The change in the 'lookForMe' method was to limit when the image of the actor is set to only when the state of intersection of a Me object changes (only at the time the Me object starts intersecting and at the time the Me object ends intersecting). Having the image set every act cycle is a CPU-hogger.

@danpost That worked perfectly. Thanks very much!

Sorry guys I just realized what was wrong. I was making the isMouseDown boolean false unless I clicked. Fixed it in the following.

Ok, great!

you can do something like this: <Code Omitted> just make sure the ima

Thanks

I was going to post this: But, then I realized that you probably have bigger problems. Aren't you getting error messages saying something about calling non-static method in a static context? If you have several Tile objects and are trying to get the values from each one individually, the Tile class in itself cannot help. You need to refer to each Tile instance and get the values from them (how can the Tile class itself know which tile you want the value of?). By your use of 'null'

Thank you. I solved this problem:

If you are unsure of how to do this, place the actors in your world manually and then go to the menubar and select 'Controls>Save the World'. This will create the code for you. Look in your subclass of World and inspect the code to see what it did. Start with only one or two objects so as not to complicate things too quickly. This is a good way to see your placing actors in code; but, once you learn how, move on and start coding it yourself (both, for the experience of doing it yourself and for more conciseness of code -- you will notice an abundance of excess code if you keep moving thing

As far as getting the score to the scoreboard in the game over world, you first need a 'get' method in the Score class to return the value of 'int Score'. Then, you will need a local reference to the new game over world that you create in the Human class so you can change the 'int Score' value of its scoreboard to that of the scoreboard in the PoringShoot world:

Open your scenario. choose Share from File menu.Now select publish Tab.