If it compiles, you can just upload it to this site so we can download and look at it for you. If it does not compile, you could comment everything except the import lines, class declaration lines and the world 'super' call and then, still, upload it after compiling.
If it compiles, you can just upload it to this site so we can download and look at it for you. If it does not compile, you could comment everything except the import lines, class declaration lines and the world 'super' call and then, still, upload it after compiling.
I have uploaded , my Cylinders jumps back , can't figure out why.Dan I would be really grateful if you could fix it and tell me what was wrong with it.
P.S I have biten more then i chew.
If it compiles, you can just upload it to this site so we can download and look at it for you. If it does not compile, you could comment everything except the import lines, class declaration lines and the world 'super' call and then, still, upload it after compiling.
Export it to greenfoot.org instead of uploading it to an extern site.
If it compiles, you can just upload it to this site so we can download and look at it for you. If it does not compile, you could comment everything except the import lines, class declaration lines and the world 'super' call and then, still, upload it after compiling.
Export it to greenfoot.org instead of uploading it to an extern site.
Sorry for noobish coding. I am just new at it , well some of you will be so kind fix it for me i would be really grateful , because I have tried lots of solutions . But it keep doing this can't understand what is it.
I can say that there is an over-abundance of fields in your classes. Plus, there is an excessive use of 'static' fields (some of which are not properly maintained). I see that you intend to eventually implement scrolling, which will be quite a feat -- trying to maintain proper values for some of the fields.
You should start simple. Work on one thing at a time (starting with the basic necessities of the project). Complete one phase before moving onto the next. Build the project in a way that would seem logical. First, the basic world; then, the main actors -- start with the walls, then move on to the main characters (disks). It might make it easier if you created an actor class to run the disk movement system. It could then set its location at the disk that is not moving and control the location of the disk that is. So, it would have a field for each of the disks and the world would have a field for the system itself. That should be pretty much it as far as fields are concerned (other than constant fields like world width, world height and things like that).