[cxS]

You're not getting what I'm saying no matter what words I put it in.
The MSDN is created from humans, which are not perfect. Sometimes there are accidents.

And...? I would agree, but do you have any clue, for how unlikely it would be that ALL of these sources are false? You act like I am the mentally challenged one here, yet to me it just looks like your making excuses to dig your way out of the facts here.

You're trying to turn my words into me saying the MSDN is wrong, or for the specific situation. Which is not what I'm saying at all, so get it through your thick skull. Otherwise, see a doctor. No joke.

And where did I ever claim that you said MSDN is wrong. I was simply pointing out how much confusion you just created because:

- You were implying that people make mistakes, and relating this to MSDN documentation
- You mentioned that you were NOT saying MSDN is wrong

Combine those two points together. What logical conclusion does that make? That you are going to say that I am wrong, based on mere chance that MSDN might have screwed up? Along with ALL the other references I have given.

You can't even understand what I am pointing out in my own posts, I clearly understand what you are saying, but the fact is that it logically, does not make any sense.

Nobody ever established what this "game" was. So who are you to say what it was or what it wasn't? Same applies for me, but think of it for yourself too. Clearly we were talking about two different things, if you didn't realize that then you're a moron.

Clearly by this logic you would be a moron as well, since you too, did not realize this. So lets just forget about the game from this point forward.

Did I ever said you said you proved me wrong? No. So what are you trying to get out of saying that?

Lol!! No, and that is a result of your arrogance. You have ONLY said that I have NOT proved you wrong, yet with no real reasons as to why I haven't, even with all of the information I have provided.

How are you not right? Because you're not. Your mind says that you're right, I'm wrong, and you know what you're talking about 100% of the time which isn't the case.

Yeah yeah, same false claims I've been hearing over and over like a broken record, yet you have no proof to provide me with. Because you say that I am wrong, it must be true eh? F*ck, aliens gather around the sun for a galactic meeting then once a month, and because I said so. *chuckle*

It's not proof. Just because you link someone to a few articles means it's true? You have A LOT to learn, my friend.

It is if you learned how to read the information properly... Perhaps learning to read should be on your list of things to learn.

The overall sense of this argument is to say that you're not right all the time, so don't try to act as if you are. There's more to invoking than you think. And if you're too dumb enough to realize that, then we can go on and on.

So I'm not right all of the time, but that doesn't mean I am never right, nor does it mean that I am not right, right now. So cut the crap... You're trying to state the obvious and avoiding what is really relevant here. You might as well try to physically run around the world on a treadmill because just the same, you're getting nowhere here.

"There's more to invoking than you think" - And like what? That it can be applied to different applications/scenarios but still essentially means to call or to execute? If you haven't noticed I have pointed that out in my links I referred you to; my proof. You can invoke many things, but the meaning of it still doesn't change.

And based on that, then YOU explain what all there is to invoking? I doubt you could do that, as you don't know what it is. Yet somehow you're becoming a self-proclaimed headstone for the know-it-all about Invoking?

Post your code about "Invoking a key" lol.

I bet you shizelkid is laughing his ass off right now at the fact that you like to act that you know more than you actually know in terms of reality.

[i0xIllusi0n]

I do realize that it is unlikely these sources would be false. That's not the point, child. I'm not acting like you're mentally challenged, I'm asking if you are because you can't understand even the simplest things I'm saying.

You didn't say I said MSDN was wrong, you were trying to imply that's what I said.
Perhaps you're not understanding me, yet again, so let me dumb it down for you. Hopefully you'll get it this time. Or I have no hope for you.
The MSDN is created by humans, so it can more than easily be wrong. But it's not usually wrong. It's rather rare. I'm stating that there's the possibility.

I know exactly what I'm talking about, it's you who is taking this whole game situation out of hand.

You didn't prove me wrong, you just think you did because you're so cocky and you want to believe anything that gives you the upper advantage.

As said before, I don't need proof. Nobody needs proof to say others are so cocky that they think everything in their mind is true. That's a given. The difference between you and me is that I acknowledge the fact I'm wrong sometimes. You don't this entire argument you've been sitting here saying you're right and I'm wrong.

Again, I know exactly what I'm saying. You're the one whose taking it a different way and responding incorrectly because you're unable to comprehend what I'm actually saying. It's happened many times that you've misunderstood my simple sentences.

I realize that you're not wrong or right all the time. I'm not claiming you're either. Cut the crap? Lol you sound like you're so out of shape you'll say anything to make sense to yourself. again, you're still refusing to acknowledge that you're wrong. Or even at that, you're still failing to acknowledge that you even just MAY be wrong. You still are forcing yourself to believe you're right no matter what the argument goes to.

If I'm getting nowhere, why are you still here? To your mind, I'm not getting it. This has been here for days, so why are you still trying? If you believe I'm not getting it, then give up. You won't give up because you know that what I'm saying (about you, not necessarily about the invoking) is true.

Also, I see you're still here actively on the thread and not leaving. You're back to the whole situation of not caring what you say as long as it contradicts what I say. And I have looked at what your posts are compared to where you are and what the situation is. You post less intelligent-wise when you're actively on the thread just waiting for me to post and you to contradict what I say.

[cxS]

The MSDN is created by humans, so it can more than easily be wrong. But it's not usually wrong. It's rather rare. I'm stating that there's the possibility.

Okay, so after all these years, nobody has caught this error (assuming it does exist), and that all other sites other than MSDN (which say the same thing as MSDN essentially), are also wrong? Nobody knows what they are talking about, and you do? That is what you are saying here, whether you realize it or not.

And thinking about the possibility that after all these years MSDN is wrong, including all other external sites, you are willing to take that, and accept it as a possibility, just in order to say that I am wrong?

Please, lets just look at that for a second now. Have you no rationalization skills or, are you just that stupid? I have to be straightforward here.

You didn't prove me wrong, you just think you did because you're so cocky and you want to believe anything that gives you the upper advantage.

The ONLY reason why you haven't accepted that you are way off base here, is the fact that you just picture me as being the cocky one that just wants to prove that I am right, and that's where all of your denial comes into play.

So I an not right because I am cocky? MSDN is cocky? ALL the other people on StackOverflow are cocky, and that is your final best reason?

Just listen to yourself here...

You won't give up because you know that what I'm saying (about you, not necessarily about the invoking) is true.

You turned it into something personal, I could care less, because you, just like I am to you, are a "random person on the internet" that has no clue about who I am. I would have continued regardless, because nobody would want to learn from false information. And that is what you are trying to force on others here.

Also, I see you're still here actively on the thread and not leaving.

Now I never said I was leaving this thread/conversation quite a few posts ago did I? You on the otherhand, well that is a different story, so good point you're making for me right here.

[i0xIllusi0n]

What don't you get that things can be actively updated? A lot of things are edited even when they don't need to be, there's a possibility that wrong information can be entered. I'm not saying it's likely, I'm saying it's a possibility. Did I say nobody knows? No. I'm saying you don't. Why am I saying that? Because for the last hour you didn't understand quite a few of things I said that were so simple anyone could. Which again, you're failing to understand what I'm saying.

And again, are you mentally challenged? I'll say it again. I'm not saying MSDN and other 3rd party websites are wrong. That's just what your moronic brain is getting from what I say. Did I ever say MSDN was wrong? No. I said there's a possibility. Did I ever say any other 3rd party websites are wrong? No.

I think you should take a careful look at what you're saying, because you're still failing to fully comprehend what I am saying, hence why you are making such wrong responses.

And again, I've said this many times, I know I can be wrong. I admit it. You don't. I know I can be wrong, but you think you're always right. That's the difference, is I accept the fact when I'm wrong. You're not even open to the fact that you MAY be wrong. So you're being cocky and ignorant. Listen to yourself. You're saying I'm saying stuff that I'm not, then you try to call me out on the things that never happened. Such good skills you have there.

I turned it into something personal? Lol no. This entire time I've been sitting here not insulting you. And you've been sitting here insulting me. "Go hit puberty" "Your rep is the opposite because you're unintelligent" - You're the only one who has tried to bring in insults. Lol, you would've continued regardless. I highly doubt that. You and I both know what you're up to.

You're right, I have said I was going to leave this thread. Clearly I'm not. So, what's your point? I come back because you have such a moronic mindset, and me being the so-called perfectionist trying to correct people of their wrongs, and coming back to say what you did wrong. Plus the fact that what you're saying is pure stupidity and laughter for me because you can't even comprehend simple sentences, you take it in a different way, then respond in a way that causes more trouble. if you would actually take the time to realize what I'm actually saying, we wouldn't be here, because you wouldn't have went off topic. Also, when I said you're actively on the thread and not leaving, I'm didn't mean leaving and never coming back. IF you'd actually understand what I'm saying, you'd realize that what I meant was that you're not leaving the thread, you're sitting there hitting refresh till you see a new post from me. You're not going back to the AF homepage or anything, you're actively on this one specific thread.

[cxS]

What don't you get that although things can be actively updated, they usually do NOT change completely, every time there is an update? Even if wrong information can be entered in, what I have seen for the way Invoking has been defined, described, and the way it has been used in context, has not changed for the last several years to my knowledge. You're missing the point entirely here, and you keep going back to the same thing over and over. I get what you are saying, but it has no relevancy to whether I am right or wrong here. The comments from others on many other sites and forums, do not change, and none of these developers would ever explain Invoking the way you have done.

I already told you, and shown you, that I am saying nothing different than all of the other people that have been referenced in the links I have given you, so if you are saying that I am wrong, that logically makes ALL of these other people wrong as well. You don't even have to say it for that to be a fact, because right or wrong is not based on the person you dumbass, it's based on the actual information being provided, and nothing that I have said in terms of information I have given you, has deviated from what ALL of these other people are saying. That effectively means that you are saying that these other people are wrong too.

I'm not saying MSDN and other 3rd party websites are wrong.

Where did I say you were? I said, that even though you are saying it is a possibility, you seem to be saying that I am wrong, based on the possibility that MSDN could be wrong. I've said this enough times now... If you don't understand what I am talking about then don't even try to reply.

Here is what I said:

• Okay, so after all these years, nobody has caught this error (assuming it does exist), and that all other sites other than MSDN (which say the same thing as MSDN essentially), are also wrong? Nobody knows what they are talking about, and you do? That is what you are saying here, whether you realize it or not.
  
  And thinking about the possibility that after all these years MSDN is wrong, including all other external sites, you are willing to take that, and accept it as a possibility, just in order to say that I am wrong?
  
  Please, lets just look at that for a second now. Have you no rationalization skills or, are you just that stupid? I have to be straightforward here.

Which basically meant:
1. Lets assume that MSDN did make a mistake
2. Now imagine the possibility of everybody else being wrong, in addition to MSDN

Rationality: It's highly unlikely, yet this seems to be THE reason you are using, for why I am wrong. This "possibility", and nothing else.

Regardless of where you look/search, or what date things have been posted by other developers, if you look at any high ranking dev site/forum, you will never see Invoke/Invoking described in the way you explain it as. That's the bottom line, because you are wrong...

Do you get it?

edit:
http://www.thefreedictionary.com/invoking

6. Computer Science To activate or start (a program, for example).

>> a program, method, service, etc... To call, execute... There is no "listen" in any of that.

http://homepages.ius.edu/jfdoyle/c335/Html/Windows.htm

Document last modified: 08/25/2003 10:49:47

Even in that link, invoke is a direct alternative to the Call instruction. Because that is all invoking is; making a call, executing, taking action, or actually doing something. And for something so simple, for some reason you can't understand it.

Old information, all the way to new information posted, Invoke has not changed, because it is a basic concept. There is nothing complex about it, which further makes the possibility of some MSDN documentation having "wrong" information even less likely. It would be like getting the description of the sun, wrong. It never will mean to "listen" to anything because it already has a logical and well defined/understood definition. Think about how stupid it would be to have invoke as a alternative keyword for Call (in that above link), if it meant to "listen".

YES - Words have multiple meanings, but definitely not meanings that mean the complete opposite of each other. If that was the case, how would you use the word in context? Or how would the word even have any defined meaning? If word "Blah" meant both on and off in 2 different meanings for the word, how would you use that word, to explain something to somebody? You moron... Just further common sense to prove that you are wrong for what you think invoking is. We already know that Invoking means to call something (based on the links I have given), so by no means could it also mean to listen. It would be very unethical to have such contradicting definitions embedded within the same word.

And for you to be right here... That is what would have to happen. Invoke would have to mean both to call, and listen. These are both complete opposites. One is action based, and the other is not.

Now, the end. Hope you enjoyed looking like a fool, because you can't prove that I am wrong based on "possibility" of an "accident" as you so call it, you have not provided anything other than the fact that your friends believe the same as you. And I have provided you with many links to support my responses now, and if you take initiative to search this up on your own, you will find much more like the links that I have given out; none agree with your idea of Invoking.

[i0xIllusi0n]

There is no point in this MSDN subtopic. You're the one who brought it up. Did I ever say MSDN was wrong? No. Did I say Microsoft doesn't know what they're doing? No. I'm saying it is a POSSIBILITY of it being wrong. And you can't deny that, because there is. Even if you want to make your little childish self think otherwise. You're wrong. People make mistakes, even Microsoft. I suggest you wake up and see the errors in life.

If you google invoking keys, you'll see lots of stuff about that. So just because you linked a few styff here and there doesn't mean shit. I could do the same, and show exactly what I'm talking about, and it would prove you wrong. That doesn't mean it's actually true or not, just like in yuor situation. Linking to a few articles doesn't mean shit. Clearly you don't know how to do research. Plus, you're only ooking for one side of the situation. Not both. Because you want to make yourself believe one side only, and are completely oblivious to my side.

"I'm not saying MSDN are wrong" - and you never said I did? I never said you did either. You're implying it because yet again you misunderstood. You seriously have a mental retardation if you're still misunderstanding what I'm saying after being told several times to not be such an idiot, and actually paying attention.

I again go back to the fact that there's both sides of the story. Linking a few articles doesn't mean anything, except that there's a group of people think you cannot invoke keys. I can do the same for the people who do think you can invoke keys. Are you saying they're wrong? Well, you are. And that's because you're mentally stuck to one side of the situation and not even acknowledging the fact that there's another side, as I've said before.

Now in the end I hope you look like a fool, because you're so oblivious to the real world, you're in your own little state of mind where everything you say and do is right, while everyone else is wrong. You need to get out of there unless you want to be an idiot for the rest of your life. Looking up "proof" for only your side of the situation is not research. That's bias. Look up some other articles about my side. You can't. Do you know why? Because you're cocky and ignorant. If you'd actually pay attention, which I can say that's a universal issue, because there's been many occasions even if just this thread that show you don't care about anything else except your own words and thoughts. I don't need proof. If you Google my side there's also many articles saying you can invoke keys. The difference is I'm open to other studies. You're not. I have many friends who say that you can invoke keys, and that what i'm saying is right. Then, comparing them to you, being the cocky kid you are, who am I going to believe? My friends, or the kid across the street who thinks he's the best in anything and is completely oblivious to everything going on around him? Wake up and smell the air. You're an idiot if you're still acting like this.

[cxS]

There is no point in this MSDN subtopic. You're the one who brought it up. Did I ever say MSDN was wrong? No. Did I say Microsoft doesn't know what they're doing? No. I'm saying it is a POSSIBILITY of it being wrong. And you can't deny that, because there is. Even if you want to make your little childish self think otherwise. You're wrong. People make mistakes, even Microsoft. I suggest you wake up and see the errors in life.

If you google invoking keys, you'll see lots of stuff about that. So just because you linked a few styff here and there doesn't mean shit. I could do the same, and show exactly what I'm talking about, and it would prove you wrong. That doesn't mean it's actually true or not, just like in yuor situation. Linking to a few articles doesn't mean shit. Clearly you don't know how to do research. Plus, you're only ooking for one side of the situation. Not both. Because you want to make yourself believe one side only, and are completely oblivious to my side.

"I'm not saying MSDN are wrong" - and you never said I did? I never said you did either. You're implying it because yet again you misunderstood. You seriously have a mental retardation if you're still misunderstanding what I'm saying after being told several times to not be such an idiot, and actually paying attention.

I again go back to the fact that there's both sides of the story. Linking a few articles doesn't mean anything, except that there's a group of people think you cannot invoke keys. I can do the same for the people who do think you can invoke keys. Are you saying they're wrong? Well, you are. And that's because you're mentally stuck to one side of the situation and not even acknowledging the fact that there's another side, as I've said before.

Now in the end I hope you look like a fool, because you're so oblivious to the real world, you're in your own little state of mind where everything you say and do is right, while everyone else is wrong. You need to get out of there unless you want to be an idiot for the rest of your life. Looking up "proof" for only your side of the situation is not research. That's bias. Look up some other articles about my side. You can't. Do you know why? Because you're cocky and ignorant. If you'd actually pay attention, which I can say that's a universal issue, because there's been many occasions even if just this thread that show you don't care about anything else except your own words and thoughts. I don't need proof. If you Google my side there's also many articles saying you can invoke keys. The difference is I'm open to other studies. You're not. I have many friends who say that you can invoke keys, and that what i'm saying is right. Then, comparing them to you, being the cocky kid you are, who am I going to believe? My friends, or the kid across the street who thinks he's the best in anything and is completely oblivious to everything going on around him? Wake up and smell the air. You're an idiot if you're still acting like this.

There is no point in this MSDN subtopic. You're the one who brought it up. Did I ever say MSDN was wrong? No. Did I say Microsoft doesn't know what they're doing? No. I'm saying it is a POSSIBILITY of it being wrong. And you can't deny that, because there is.

And back to the same old shit again, even though I have already covered this. Your IQ can't be greater than 90, because you are really really stupid. I already admitted that I acknoleged this, but what's the difference whether you say it is wrong, or whether you say there is a possibility? You're still ignoring the facts I have pointed out through MSDN, so this definitely means that you are just unwilling to believe MSDN, and furthermore, meaning that you must think it is wrong if you don't believe MSDN.

Otherwise, if it's not wrong, then it must be right, and therefore, this would mean that you do not know what you are talking about with Invoking...

And inversely, if you don't think it is right, then you are either saying that it is wrong, or you are utilizing this "possibility" that it might be wrong, just in order to say that I am wrong, for using MSDN references as proof for why YOU are wrong.

Do you not get that?... What a moron...

Why are you pointing out this possibility in the first place? There must be a reason, as you OBVIOUSLY seem unwilling to believe MSDN as PART of my proof. The fact that you are unwilling to believe MSDN is irrelevent though (whether you do or you do not), because I have found links other than MSDN which ALL say the same thing.

If you google invoking keys, you'll see lots of stuff about that.

None of which is related to acting as global hotkeys or a keyboard hook. If there's lots of stuff about Windows 8 on google, does that mean anything, other than there's just, a lot of information about it online? :S Because I don't think so.

So just because you linked a few styff here and there doesn't mean shit. I could do the same, and show exactly what I'm talking about, and it would prove you wrong.

Do it then! I'd like to see, because any proof you provide will probably be about as twisted as your own common sense...

That doesn't mean it's actually true or not, just like in yuor situation

Yeah okay, I've provided several links now from big reputable sites, with lots more that I could link you to in addition to what I have already referenced, but all of this proof doesn't make it true...?

Btw, I looked up "Invoking Keys .NET" for your own sake, just to show that it has nothing to do with the way you describe it.

How to Register a hotkey: http://windowscoding.com/blogs/blake/arc...ation.aspx

• The only invoking he is doing here is to the p/Invoked functions.

This is what invoking a key would be: http://stackoverflow.com/questions/87270...oard-event

"simulating a key press" - As I mentioned.

And best link: http://social.msdn.microsoft.com/forums/...9A6493AD76

Invoking the Del key for testing purposes

I am writing tests for an app and I need to simulate a user hitting the Del key.

"simulate" - again... And this was posted in 2008.

The next guy suggests the SendKeys class: http://msdn.microsoft.com/en-us/library/....send.aspx

Because this allows the person to invoke/'simulate' keystrokes.

Now again, like I've been asking for the last 6 pages. Provide some of your proof! ?

I could do the same, and show exactly what I'm talking about, and it would prove you wrong.

You've now said that you could prove me wrong, so lets see it.

edit: And at least my colored portion of my post meant something lol. That's just a bunch of flaming with no meaning, and no supporting evidence; assumptions. But not in regards to anything about Invoking, so it's just "clutter" to this discussion.

Btw "Proof":

evidence sufficient to establish a thing as true, or to produce belief in its truth.

Something you have not provided. It's evident that you know you are wrong, because even when I ask for proof, the best you can do is insult me personally. It sticks out like a sore thumb.

[shizelkid]

I bet you shizelkid is laughing his ass off right now at the fact that you like to act that you know more than you actually know in terms of reality.

I really am. you 2 are funny.

[cxS]

This guy can't even learn something when the material for accurate information is put right in front of him...

[Dismas]

There is no point in this MSDN subtopic. You're the one who brought it up. Did I ever say MSDN was wrong? No. Did I say Microsoft doesn't know what they're doing? No. I'm saying it is a POSSIBILITY of it being wrong. And you can't deny that, because there is. Even if you want to make your little childish self think otherwise. You're wrong. People make mistakes, even Microsoft. I suggest you wake up and see the errors in life.

If you google invoking keys, you'll see lots of stuff about that. So just because you linked a few styff here and there doesn't mean shit. I could do the same, and show exactly what I'm talking about, and it would prove you wrong. That doesn't mean it's actually true or not, just like in yuor situation. Linking to a few articles doesn't mean shit. Clearly you don't know how to do research. Plus, you're only ooking for one side of the situation. Not both. Because you want to make yourself believe one side only, and are completely oblivious to my side.

"I'm not saying MSDN are wrong" - and you never said I did? I never said you did either. You're implying it because yet again you misunderstood. You seriously have a mental retardation if you're still misunderstanding what I'm saying after being told several times to not be such an idiot, and actually paying attention.

I again go back to the fact that there's both sides of the story. Linking a few articles doesn't mean anything, except that there's a group of people think you cannot invoke keys. I can do the same for the people who do think you can invoke keys. Are you saying they're wrong? Well, you are. And that's because you're mentally stuck to one side of the situation and not even acknowledging the fact that there's another side, as I've said before.

Now in the end I hope you look like a fool, because you're so oblivious to the real world, you're in your own little state of mind where everything you say and do is right, while everyone else is wrong. You need to get out of there unless you want to be an idiot for the rest of your life. Looking up "proof" for only your side of the situation is not research. That's bias. Look up some other articles about my side. You can't. Do you know why? Because you're cocky and ignorant. If you'd actually pay attention, which I can say that's a universal issue, because there's been many occasions even if just this thread that show you don't care about anything else except your own words and thoughts. I don't need proof. If you Google my side there's also many articles saying you can invoke keys. The difference is I'm open to other studies. You're not. I have many friends who say that you can invoke keys, and that what i'm saying is right. Then, comparing them to you, being the cocky kid you are, who am I going to believe? My friends, or the kid across the street who thinks he's the best in anything and is completely oblivious to everything going on around him? Wake up and smell the air. You're an idiot if you're still acting like this.

There is no point in this MSDN subtopic. You're the one who brought it up. Did I ever say MSDN was wrong? No. Did I say Microsoft doesn't know what they're doing? No. I'm saying it is a POSSIBILITY of it being wrong. And you can't deny that, because there is.

And back to the same old shit again, even though I have already covered this. Your IQ can't be greater than 90, because you are really really stupid. I already admitted that I acknoleged this, but what's the difference whether you say it is wrong, or whether you say there is a possibility? You're still ignoring the facts I have pointed out through MSDN, so this definitely means that you are just unwilling to believe MSDN, and furthermore, meaning that you must think it is wrong if you don't believe MSDN.

Otherwise, if it's not wrong, then it must be right, and therefore, this would mean that you do not know what you are talking about with Invoking...

And inversely, if you don't think it is right, then you are either saying that it is wrong, or you are utilizing this "possibility" that it might be wrong, just in order to say that I am wrong, for using MSDN references as proof for why YOU are wrong.

Do you not get that?... What a moron...

Why are you pointing out this possibility in the first place? There must be a reason, as you OBVIOUSLY seem unwilling to believe MSDN as PART of my proof. The fact that you are unwilling to believe MSDN is irrelevent though (whether you do or you do not), because I have found links other than MSDN which ALL say the same thing.

If you google invoking keys, you'll see lots of stuff about that.

None of which is related to acting as global hotkeys or a keyboard hook. If there's lots of stuff about Windows 8 on google, does that mean anything, other than there's just, a lot of information about it online? :S Because I don't think so.

So just because you linked a few styff here and there doesn't mean shit. I could do the same, and show exactly what I'm talking about, and it would prove you wrong.

Do it then! I'd like to see, because any proof you provide will probably be about as twisted as your own common sense...

That doesn't mean it's actually true or not, just like in yuor situation

Yeah okay, I've provided several links now from big reputable sites, with lots more that I could link you to in addition to what I have already referenced, but all of this proof doesn't make it true...?

Btw, I looked up "Invoking Keys .NET" for your own sake, just to show that it has nothing to do with the way you describe it.

How to Register a hotkey: http://windowscoding.com/blogs/blake/arc...ation.aspx

• The only invoking he is doing here is to the p/Invoked functions.

This is what invoking a key would be: http://stackoverflow.com/questions/87270...oard-event

"simulating a key press" - As I mentioned.

And best link: http://social.msdn.microsoft.com/forums/...9A6493AD76

Invoking the Del key for testing purposes

I am writing tests for an app and I need to simulate a user hitting the Del key.

"simulate" - again... And this was posted in 2008.

The next guy suggests the SendKeys class: http://msdn.microsoft.com/en-us/library/....send.aspx

Because this allows the person to invoke/'simulate' keystrokes.

Now again, like I've been asking for the last 6 pages. Provide some of your proof! ?

I could do the same, and show exactly what I'm talking about, and it would prove you wrong.

You've now said that you could prove me wrong, so lets see it.

edit: And at least my colored portion of my post meant something lol. That's just a bunch of flaming with no meaning, and no supporting evidence; assumptions. But not in regards to anything about Invoking, so it's just "clutter" to this discussion.

Btw "Proof":

evidence sufficient to establish a thing as true, or to produce belief in its truth.

Something you have not provided. It's evident that you know you are wrong, because even when I ask for proof, the best you can do is insult me personally. It sticks out like a sore thumb.

Calling people stupid isn't nice.