Discussions

I think that == seems to work sometimes because Java handles strings a little differently than most objects, it has something called a "String Literal Pool" where it has all the strings that are coded into your program already sitting there in memory, or something like that, and it is optimized to use as few strings as possible, so if you have literal strings in your code, and you reference them, a lot of the time you will be referencing the same string anyway and == works. But other times it won't work. Just remeber the difference between references, primitives, and objects. == compares refer

Thanks! And I would say that doing "if (someVariable != null)" could help with many methods that can return null?

Thank you so much for the explanations!!!!! they helped me understand and figure it out!!! Thanks again AwesomeNameGuy and DanPost!! I really appreciate your help!

Upupzealot: What code did you try, and what error message did you get?

I know which method causes the warning, and indeed, it has to do with generics. But whether or not the warning will pop-up seems to depend on the jdk that is used Btw, the link to the Ausgangsszenario is: http://greenroom.greenfoot.org/resources/51 It would be nice if the code could be adjusted in such a way that the warning is not given anymore. Sjaak

The language you're using in Greenfoot is plain old Java - you can use any Java libraries you like, code just as you would in real world Java - the conventions are the same, the syntax is the same, the language is the same. In short, pretty much all the concepts you learn in Greenfoot can be applied to "real world" situations, Java or not - and if you develop using Java (which is a highly used language in the real world, Google uses it extensively for instance) they'll translate directly. Greenfoot does make things easy from a graphical perspective and there are of course additional conc

the s is the string for the image, the 12 is font size,the next thing is text color, the last thing is background.

Thanks for your reply, it is very helpful :).

"BlueJ","Greenfoot" and "Redhat" seems to be the three sisters of a family ! haha~

Huzzah! Fixed it! It was as simple as this: It said it didn't like me accessing the non-static variable, so I changed this <Code Omitted>to this <Code Omitted> and what do you know, it worked :D.

Thanks :D.

You probably want to look at the getObjectsInRange method which will allow you to get a list of all the objects a certain radius (or closer) away from the actor.

Well if it has objects in the way that makes it a bit more complicated. You could keep track of your position by judging how much you've turned / travelled then work out from that if something you've hit is a likely edge or obstacle. That might give you a starting point. With these sorts of problems it's often easier to map out your logic on paper first, then turn it into code later.

The short answer is likely if you have to ask the question, then you're probably not at a stage where you can implement it. It is indeed impressive and a nice piece of coding, but any 3D or iso-3D like worlds you see in Greenfoot have had the 3D in them coded by hand, it's not something that's built into Greenfoot at all! Of course, this doesn't mean you can't look at the source code, try to gain an understanding of it and learn from it :)

I changed it to double and it no longer has an error, disregard this :D.