Discussions

In your atWorldEdge method, you are only checking to see if the actor is in the world for the first part of the conditions. Because you are ORing the conditionals, you would need to check before each one. Something like this: <Code Omitted>More simply, you can modify the method like so:

We need to see more code, I think. I don't see anything wrong with what you've posted (except that stateVotes probably refers to a different variable in both cases).

Thx a lot :D ^^ you guys are the best :D

For instance, the world contains (aggregates) actors. Been poking around - new to java and greenfoot. This program is fantastic at showing some of the simple theory of OO. Using it to help me "teach assist' some of my theory classes - breaking down parts of my topic into very small, simple examples for students to play with. It's not a "programming language class", more of a theory of - class that complements their other classes. Thanks for the poke in the right direction.

I made it using the suggestion in this post: click here You have an object in the world for each different thing which can be hovered. (These can be objects of the same class. When creating them, you let them know what their job is.) When it is hovered, you add a new actor to the world. You give this object an image with the text description. When it is not hovered anymore, you simply remove the added actor from the world again.

Ok :D thank you very much ^^

Aha. Got it. Needed two equals signs. Thanks for the help! :D

Thank you so much! It really works. :)

I did all of this and then opened my exported project in IE, and still got the same thing. The enhanced protected mode and 64-bit stuff was already turned off, Java was already enabled... so I simply added that

thanks for the compliment!!!!!

Thank you now it works!

@Super_Hippo Thanks a lot, it works perfect. I just misunderstood the x and y parameter of the drawOval method .....

Okay thank you very much ^^ have a nice day sir

Usually line 4 should replace line 5. If you use it in the prepare method before the User is added to the world though, it will never be true. I think you should pass the User object to the new world and add that user to the new world instead of creating a new one. Then you can check if its entry variable is true or false.

First, the score class shouldn't extend the ball class because the score isn't a ball. There are several ways to do it. One would be to save the scores in the world.