Again, these comments make it sound like you did not actually even read my first post the first time you looked at it. You merely glanced at it, and immediately judged it as "difficult to read". And...uh, I DID separate the text of the first post into paragraphs. It is not a "wall of text", as you put it. The first paragraph was long, I'll admit to that, and could have probably been split up into more paragraphs, but it was not a "wall of text"... 7 lines can not be described as that. I chained those lines together since they were connected, and part of the same thought process or "train of thought". And what's wrong at stating what I was trying to do, and how I had decided to go about doing it?? I could have done worse, and made the post really long and extremely detailed about everything I had done, and tried, and all of that...but I figured a shorter post (one to the point...) would be better and cause more people to actually want to read it, that's why I wrote it like that. I think you're just nitpicking now...
Now, as for the explaining of the code, perhaps these advices may help you reduce the complexity of your posts in the future.
First, avoid writing a wall of text. It discourages people. Try to write as little as possible, if possible.
Separate your text into paragraphs. It might even be good to use a blank line between paragraphs to increase readability. Believe me, it helps a ton. Find places to split your text into paragraphs! Force it, if necessary.
And lastly, try to show what you mean with code and simplify your explanation. Don't write "first I did X, then Y, then Z, and that caused A, and then B, and finally C. Then I tried D because I was bored but realized that E was better because of F...". Show your approach with code instead. Easier to read. Really. Chaining lots of things like that makes it hard to read. Split it. Write code, explain why you did it and what happened. Then do the next, and so on. It may be a little longer but it's easier to read.
Bah...as if I didn't understand what you wrote and what you meant by it. It doesn't take a rocket scientist.
I know, writing on message boards and asking for help is a science in itself, but it never hurts to try these things, even if it might be difficult to understand what exactly they mean.