Actually, the response was that what you wrote should work as given. If it doesn't work for you then the fault must be somewhere else in your code.
dariuc wrote:Nine times out of ten if i experimented on it first and did it wrong in all the ways i tried to implement it without knowing i was wrong to begin with i wouldn't learn ANYTHING
That's how learning works.
Thomas Alva Edison wrote:Genius is 1% inspiration and 99% perspiration
why don't you actually try code first. How stupid does that even sound? I asked a question
When looking through these forums before you posted you might have seen that this a very common response to your type of post. Usually trying it for yourself is a lot faster than posting and waiting for a response. (See also the second link in this post.)
you weren't even offering to help fix the problem.
You asked a question, you got an answer. It was a correct answer for the question that was given (it's not our fault if it was the wrong question). You said that it didn't work for you, for which the only rational explanation is that the problem isn't with what you asked but something else.
Point blank IT didn't work for me, who cares why?
Well, I certainly don't; dagon probably doesn't either. It's your code and you're the one who's responsible for it, so I presume you do.
Sorry to hear that you weren't able to learn what was wrong with your code, but I'm glad you managed to work around it.
no one put a gun to either of your heads and made you reply
Gee, maybe we do care. At least enough to answer.