Official Everybody Edits Forums

I, too, must inject my own opinions, beliefs, and whatnot.

Also seen on SO: http:// (S O ) .com/questions/13345091/c-sharp-checkforillegalcrossthreadcalls
"Or only on a particular user's machine, you'll blame the user instead of your code."
"trouble that causes is extremely hard to diagnose."

I like lrussell's string to int conversion. Very useful. I plan to implement soon.

I also like how marco felt compelled to hold the "9" key down instead of simply writing one of those fancy infinite loops
but hey who's counting
Oh, and you know how to code good? well for you! (anyone at all see what I did there)

I figure programming IS supposed to be easy. I mean, there's tons of things out there about code re-use and class inheritance... and... stuff... different ideas that make programming more than simply copy/pasting lines of code. We have loops, you don't have to type out each command in a sequence... we have functions so... something else good happens!
But in this case, "easy" is an illusion. You might think you're getting off scot-free. But, in reality, you're opening your program up for bugs. You pretend they aren't there.

Imagine working in Word or something. You have a research paper due. (Shockingly, you're cramming!) You're almost done and ready to save. As you click that one multi-thread button (no idea which one)... all of your work is lost! Oh well. Should've invoked.
(Obviously you folks will never go to work developing Word or some other high-profile program. But there's a chance you do make something where users count on your dependability and it's your job to repay that with reliable bug-free results.)

"don't use threads"
haha good one
pretty sure the onmessage is already on a different thread.
out of luck there I guess.

k well have fun