Skip to main content
Commonmark migration
Source Link

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

pay the piper

##pay the piper toto accept the unpleasant results of something you have done | pay the price
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

##pay the piper to accept the unpleasant results of something you have done | pay the price
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

pay the piper

to accept the unpleasant results of something you have done | pay the price
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

I'm not going to defend the overall hostility of the comments, which Hans has already apologized forHans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

##pay the piper to accept the unpleasant results of something you have done | pay the price
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

##pay the piper to accept the unpleasant results of something you have done | pay the price
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

##pay the piper to accept the unpleasant results of something you have done | pay the price
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

Fixup of bad MSO links to MSE links migration
Source Link

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it uplook it up instead of guessing:

pay the piper

 

to##pay the piper to accept the unpleasant results of something you have done | pay the price
  
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept"accept my answer"answer" by "pay"pay the piper"piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If"If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

pay the piper

to accept the unpleasant results of something you have done | pay the price
 After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

I'm not going to defend the overall hostility of the comments, which Hans has already apologized for, but one thing bears mentioning, and that is that several people here seem to have thoroughly misunderstood the meaning of one his comments.

People, please, if you don't know what an idiom means, look it up instead of guessing:

 

##pay the piper to accept the unpleasant results of something you have done | pay the price 
After fooling around for most of the semester, now he has to pay the piper and study over vacation

There is no way, no how, that he actually meant "accept my answer" by "pay the piper". It just doesn't make idiomatic sense. And considering that the top-voted answer in this question thread uses precisely such an interpretation, it's indicative of the fact that several people got the wrong idea.

It's plain as day to me what he actually meant. The comment meant, "If you insist on doing this the wrong way (using DoEvents to mimic an asynchronous task) then you have to deal with the negative consequences (requiring extra code to stop the task or else having the application hang). That's it. And speaking as a Winforms developer of... many years, I can attest to that being completely, 100% correct.

Again, I'm not defending the overall tone of those comments or the answer itself, but the assumption people seem to be making here - that he was demanding his answer be accepted before he would offer any more help - is completely and unequivocally wrong.

Pretty sure that a lot of the reddit folks weren't familiar with the expression either and downvoted on the same wild and false assumption.

Migration of MSO links to MSE links
Source Link
Loading
Source Link
Aarobot
  • 35k
  • 8
  • 73
  • 126
Loading