I'd guess what your problem is but I couldn't be bothered to go through another series of exchanges where you keep going "oh no that's not quite what I meant".
While I think that Reelya might be overreacting a bit here, I do kinda sympathize with what they are getting at. We'll happily help you with your problems 3man75, but if you want us to debug something you need to be
very specific about exactly what your program is supposed to be doing and what it isn't successfully doing.
This is a world where something as simple as a missing "break;", or a ++X instead of a X++ can result in a very different output when you still have 99% of the same code, and unless you tell us exactly what your code is supposed to be doing and what the problem is it can be nigh impossible for us to find the problem without totally copying your code into a program and trying to recreate the entire project. Your explanation can be in your post, in comments in the code (which you probably should be doing more of anyways
), or both, but there's gotta be some explanation somewhere. I do enough attempting to wrap my head around nonfunctional code as a grader for one of my college's CS classes to know how hard it can be, and that's when I have a specific writeup detailing their problems and a specific list of the requirements.
So yeah, we'll gladly help you, but you gotta give us all the details you can or it rapidly becomes near impossible to debug. I'd rather have too much information about what you are trying to do than not enough, personally.