I see questions like this occasionally, where it amounts to little more than a bunch of code. Usually there are some end-user details, like, when I click this button, it doesn't do what it's supposed to do.
Actually, the question to which I linked is a bit better than usual. At least he attempts to explain what should happen vs. what does happen. Either way, though, it's still a question based on end-user results, not based on anything technical. As such, it's not a question which will likely be of any use to anyone else in the future.
In the past, I would have voted to close a question like this as being too localized. After that option was removed, due to certain abuses, I would have voted to close it because questions asking for code should demonstrate a minimal level of understanding, but that option has also now been removed, due to similar abuses, I'm sure.
So where does that leave us for a question like this? The closest valid reasons for closing this question now would be that it's too broad or unclear, but neither of those reasons adequately apply. It's not really off-topic, since it is programming-related, so the "Other..." option under there doesn't even really apply.
Since there's no good options, it seems like everyone is simply resorting to down voting, but that's not very helpful to the person posting the question. I understand that the other options were removed for good reasons, but it seems like a question like this is now falling through the cracks.
Or am I wrong? Is this kind of question something that should be welcomed on StackOverflow? I personally didn't down-vote it because, as far as I can tell, it's not a bad question based on all the good reasons for closing. Personally I don't want to waste my time debugging someone else's code for them, but I suppose if this kind of question is welcome, maybe it shouldn't even be down-voted and it should just wait until someone comes along who is bored enough to be willing to help?