Discussions

Awesome! Worked great! Thanks!

iphones use Objective C and requires you to pay 99 dollars a year to develop and deploy to iphone. If you slip in the fee payment your app will disappear from itunes. You cannot deploy binaries to your own device unless you either pay the fee, or jail break the device. There may be thing out there to help did a goolge search for Java to iphone and got that there are also some kits that have their own proprietary schemes that will deploy to both iphone and android like Stencyl and

Your question is vague. Like any task, you need to break it down into small steps, and then express those steps using the programming language. Is this what you really meant to say? How about you start by describing what you want to happen, in numbered steps? (And then explain which of these steps you are unable to write code for!)

In the code you post, where is 'fruit' declared and initialised? Why do you call 'getType()' and ignore what it returns? Perhaps you meant to declare a local variable called 'fruit' and assign to it depending on the world type, something like:

Okay that first one worked, thanks!

--

Usually, the heap space error will occur when you are creating an abundance of actors or objects. Check your logic in your act methods and your loops.

You may get some weird facing actions with the way the movement is coded. You could end up moving one way while facing another if two direction keys are pressed simultaneously. Putting 'else's between the different direction checks may help; but then, if the first direction is not a valid one, the second one will not be checked..\ I would do the facing part first, before the moving part.

A Bar is basically a Counter. A Counter changes its image to reflect a change in the value that it represents; a Bar is exactly the same. The only difference is what those changes in its images are. A Counter will always show a the current value in text form; a bar may also do this. But, the bar will update its image by adjusting the length of the bar itself; that is the only significant difference between the two. Although, in order to do this, it would need to know the maximum value allowed (and the minimum, if not assumed to be zero).

What I meant by this was * move horizontally * check for left/right obstacles and move back if necessary * move vertically * check for above/below obstacles and move back if necessary Your 'move' method right now is doing both movements together before the checking.

For one thing, I am not sure if you intended this: but, your world cell-size is 20 and yet you are using 40 for a grid size. Maybe you meant to set CELL_SIZE to 20 (but I could be mistaken). Then, your wall would also need to be sized at 20.

I would just put a member in each alien type, have the hit take one away, when it is less than 1 then do the removeObject call on the alien.

Looks like you cut part of the PepperJackCheese class code from the post. Also, the Cheese class might be important. It would be best to copy/paste the entire code of each class into individual 'code' embedding windows.

Use an array of images. <Code Omitted>or <Code Omitted> The index (number) refers to each image. There is no need to work with the strings for the colors.