Quote:
I fix one thing and it messes up other things in the file.
When asking for help, it is a good idea to explain how things go wrong with an example to reproduce the problem.
Quote:
I have tried to do basically everything, but there's always something wrong with my code. I fix one thing and it messes up other things in the file.
May be it is time to try the debugger and watch your code performing, it should help you to understand what exactly happen behind the hood.
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
The downside of this solution:
- It is a DIY, you are the one tracking the problem and finding its roots, which lead to the solution.
The upside of this solution:
- It is also a great learning tool because it show you reality and you can see which expectation match reality.
secondary effects
- Your will be proud of finding bugs yourself.
- Your learning skills will improve.
You should find pretty quickly what is wrong.
Debugger - Wikipedia, the free encyclopedia[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html[
^]
https://www.jetbrains.com/idea/help/debugging-your-first-java-application.html[
^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.