Re: wm_touch and wm_gesture Message
David Ching
news:7D1BF478-8950-4723...@microsoft.com...
> Dear all:
> I'm a junior engineer in SW. And now, i try to develop a software to
> simulate a touch screen's operation without any touch hardware. In win 7,
> these two message, wm_touch and wm_gesture, can't be triggled directly by
> SendMessage and PostMessage. So In win7's touch architecture, these
> messages
> can only be triggled by a touch hardware? Or It can be triggled by other
> win
> api and other ways, like driver, to make it true?
>
Why do you say they can't be triggered with PostMessage()? Make sure the
app that is posting has the same privilege as the one handling WM_TOUCH (or
run the poster app As Administrator to be sure).
-- David
Joseph M. Newcomer
they could not be generated by SendMessage or PostMessage.
joe
On Thu, 24 Dec 2009 23:30:01 -0800, Mao <M...@discussions.microsoft.com> wrote:
>Dear all:
> I'm a junior engineer in SW. And now, i try to develop a software to
>simulate a touch screen's operation without any touch hardware. In win 7,
>these two message, wm_touch and wm_gesture, can't be triggled directly by
>SendMessage and PostMessage. So In win7's touch architecture, these messages
>can only be triggled by a touch hardware? Or It can be triggled by other win
>api and other ways, like driver, to make it true?
Joseph M. Newcomer [MVP]
email: newc...@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
Mao
after the message has been forwarded using PostMessage, SendMessage, or one
of their variants. These functions will close and invalidate this handle."
Above is the note in the MS MSDN's wm_touch description, and i had tried to
directly use postmessage and sendmessage in a button event, just like the
below example,
MESSAGE_MAP
ON_MESSAGE(WM_TOUCH , OnTouch);
void XXXX::OnBnClicked()
{
this->PostMessage(WM_TOUCH , wParam , lParam);
}
the OnTouch function has also been added in my program, but when the
PostMessage transferred the WM_TOUCH message, my onTouch function doestn't be
triggled. Furthermore, if i changed the WM_TOUCH to any other Message, like
WM_LBUTTONDOWN, the program processing is also correct(onTouch can be
triggled). So i think whether the wm_touch message can't be directly triggled
if i have no any touch hardware. Or by other ways to triggle these message.
Thanks for reply....
--
...
Mao
after the message has been forwarded using PostMessage, SendMessage, or one
of their variants. These functions will close and invalidate this handle."
Above is the note in the MS MSDN's wm_touch description. How to make sure
the privilege as the one handling WM_TOUCH? If i have no privilege to handle
WM_TOUCH, the privilege how to get?
PS: In my program, if i change wm_touch to other messages, like
WM_LBUTTONDOWN, the program process can work correctly, but wm_touch can't.
--
...
> Why do you say they can't be triggered with PostMessage()? Make sure the
> app that is posting has the same privilege as the one handling WM_TOUCH (or
> run the poster app As Administrator to be sure).
>
> -- David
>
> .
>
David Ching
> "Note also that the touch input handle in this parameter is no longer
> valid
> after the message has been forwarded using PostMessage, SendMessage, or
> one
> of their variants. These functions will close and invalidate this handle."
>
This refers to the lParam of WM_TOUCH; it becomes invalid after you post the
message again, but it doesn't say you can't PostMessage(WM_TOUCH). In fact,
by saying the above, Microsoft seems to be saying that you *can* call
PostMessage(WM_TOUCH), with the limitation mentioned (that lParam becomes
invalid).
> Above is the note in the MS MSDN's wm_touch description, and i had tried
> to
> directly use postmessage and sendmessage in a button event, just like the
> below example,
>
> MESSAGE_MAP
> ON_MESSAGE(WM_TOUCH , OnTouch);
>
> void XXXX::OnBnClicked()
> {
> this->PostMessage(WM_TOUCH , wParam , lParam);
> }
>
> the OnTouch function has also been added in my program, but when the
> PostMessage transferred the WM_TOUCH message, my onTouch function doestn't
> be
> triggled. Furthermore, if i changed the WM_TOUCH to any other Message,
> like
> WM_LBUTTONDOWN, the program processing is also correct(onTouch can be
> triggled). So i think whether the wm_touch message can't be directly
> triggled
> if i have no any touch hardware. Or by other ways to triggle these
> message.
>
Interesting. but if you post WM_LBUTTONDOWN, your app needs to changed to
add ON_WM_LBUTTONDOWN, as this is the appropriate message map entry for that
message. So maybe MFC message map is not set up correctly (although I do
see your code follows the example in
http://msdn.microsoft.com/en-us/library/dd371581%28VS.85%29.aspx).
To eliminate message map, try overriding your class's WndProc() and see if
you get WM_TOUCH there. BTW, I don't have Win 7 SDK installed. What is
WM_TOUCH #define to?
And can you try running your app in another OS besides Windows 7 (that does
not know anything about WM_TOUCH); see if you then receive WM_TOUCH message?
If so, then we know Win 7 somehow treats that message specially. (But I
don't think so, WM_TOUCH is just another predefined windows message).
-- David
David Ching
>> Why do you say they can't be triggered with PostMessage()? Make sure the
>> app that is posting has the same privilege as the one handling WM_TOUCH
>> (or
>> run the poster app As Administrator to be sure).
>>
> the privilege as the one handling WM_TOUCH? If i have no privilege to
> handle
> WM_TOUCH, the privilege how to get?
I meant in general an app with a lower privilege can't PostMessage to an app
with a higher privilege. Windows will block the receiver app from ever
seeing the message. But in your code you put in another posting you are
posting to the same app, so this isn't an issue.
-- David
Mao
> message again, but it doesn't say you can't PostMessage(WM_TOUCH). In fact,
> by saying the above, Microsoft seems to be saying that you *can* call
> PostMessage(WM_TOUCH), with the limitation mentioned (that lParam becomes
> invalid).
>
After your reminder, i can see what my problem is. In Win7, after triggering
wm_touch message, the lParam is a handle of the TOUCHINPUT and is used to get
the touch points' information. In fact, i have no touch hardware to create
this handle automatically. So, in the viewpoint of software, i can create any
a handle to make wm_touch message occurred? If so, the problem may be solved.
But if the handle's information is checked whether is a TOUCHINPT's handle or
not, it means that it must need a hardware?
Thx for your reply~~~
David Ching
> After your reminder, i can see what my problem is. In Win7, after
> triggering
> wm_touch message, the lParam is a handle of the TOUCHINPUT and is used to
> get
> the touch points' information. In fact, i have no touch hardware to create
> this handle automatically. So, in the viewpoint of software, i can create
> any
> a handle to make wm_touch message occurred? If so, the problem may be
> solved.
> But if the handle's information is checked whether is a TOUCHINPT's handle
> or
> not, it means that it must need a hardware?
I don't think Windows validates the handle before passing the message. I
think instead is it keeps a static copy of the TOUCHINPUT data until the
message is processed, at which time it thinks your app is done with it, so
it frees the TOUCHINPUT data.
Just pass NULL for lParam and capture the message in WndProc() like I
suggested and see if you get it.
-- David
Mao
pass to the event. It also can't be triggered. So the handle, lParam, plays
an important role (For OS to judge whether a touch handle or not). I think
that the handle is created and connected to the touch's hardware is also
needed in the Win 7 touch's architecture, isn't it? So, a touch handle
connect to a hardware can be simulated by an API?
--
...
"David Ching" wrote:
> .
>
David Ching
> Thanks for your suggestion. But unfortunately, I take lParam as NULL, and
> pass to the event. It also can't be triggered. So the handle, lParam,
> plays
> an important role (For OS to judge whether a touch handle or not). I think
> that the handle is created and connected to the touch's hardware is also
> needed in the Win 7 touch's architecture, isn't it? So, a touch handle
> connect to a hardware can be simulated by an API?
I'm sorry but I don't know about the hardware requirements from WM_TOUCH and
WM_GESTURE. I do know about using PostMessage to simulate messages received
from the system and have never before encountered one that calling
PostMessage() did not actually generate a message because Windows was "smart
enough" to try to interpret the lParam and figure it was bogus.
Unfortunately, I don't have time to install the Win 7 SDK and try it myself.
Did you override CWnd::WindProc() as I suggested to see if you receive
WM_TOUCH there? That's about all I can suggest, sorry.
-- David
Mao
Never mind!!!! I will keep on trying it. Thank you very much.
--
> I'm sorry but I don't know about the hardware requirements from WM_TOUCH and
> WM_GESTURE. I do know about using PostMessage to simulate messages received
> from the system and have never before encountered one that calling
> PostMessage() did not actually generate a message because Windows was "smart
> enough" to try to interpret the lParam and figure it was bogus.
> Unfortunately, I don't have time to install the Win 7 SDK and try it myself.
> Did you override CWnd::WindProc() as I suggested to see if you receive
> WM_TOUCH there? That's about all I can suggest, sorry.
>
> -- David
>
>
> .
>
David Ching
> Never mind!!!! I will keep on trying it. Thank you very much.
I confirm your findings that posting WM_TOUCH (0x0240) to the same window
results in the message not being received when run on Windows 7. When
running the same app on Vista, the message is received. So Windows 7 is
preventing the message from being posted. Calling RegisterTouchWindow() has
no effect on this. Sorry I couldn't help more. The Touch API is still so
new there are few people who know short of Microsoft.
-- David
David Ching
news:#wDlARCi...@TK2MSFTNGP05.phx.gbl...
> I confirm your findings that posting WM_TOUCH (0x0240) to the same window
> results in the message not being received when run on Windows 7. When
> running the same app on Vista, the message is received. So Windows 7 is
> preventing the message from being posted. Calling RegisterTouchWindow()
> has no effect on this. Sorry I couldn't help more. The Touch API is
> still so new there are few people who know short of Microsoft.
>
I've run your situation past a few C++ people at Microsoft. First responses
speculate ntuser is not forwarding the posted WM_TOUCH message due to
invalid parameters. It was news to me that ntuser validates message
parameters in PostMessage(), but there you go. Will let you know if
anything more definitive comes up.
Regardless, it was also pointed out that even if you successfully did post
WM_TOUCH, your app still would not be useful because you wouldn't know what
info to post (the lParam HTOUCHINFO) because you would need to match what
the hardware sends, and you don't know what the hardware sends because you
don't have any hardware. So this whole approach of posting WM_TOUCH will
probably not get very far.
Another approach is to call SendInput() to generate the WM_TOUCH messages,
but alas this API (or at least the doc of it) hasn't been updated to support
Touch parameters.
The easiest way is probably to go buy a Touch enabled Windows 7 PC, sorry.
-- David
David Ching
> I've run your situation past a few C++ people at Microsoft.
Another Microsoft MVP, Raffaele Rialdi, suggests:
> I would suggest to use the MultiTouchVista from codeplex and nui group
> projects.
> I built my own multtouch device using that stuff:
> http://www.iamraf.net/Articles/SurfRaf-home-made-surface-for-Windows-7
>
> If you want to programmatically test an application simulating touch, you
> can use tuio protocol described here:
> http://nuigroup.com/
> it's a winsock based protocol used to give Win7 MulitouchVista driver the
> correct sequence of touches.
>
If this helps you, please let him know (it's his blog in the first link).
Thanks,
David
Mao
Thanks for your help!!! I replace the way to post WM_TOUCH message with
using MultiTouchVista to simulate the Touch operation. In MultiTouchVista, it
simulates multi mice and update these mouse point by an function. And now, i
try to pass my detected position and use this function to Achieve the goal.
--
...
"David Ching" wrote:
> .
>
David Ching
> Dear David:
> Thanks for your help!!! I replace the way to post WM_TOUCH message
> with
> using MultiTouchVista to simulate the Touch operation. In MultiTouchVista,
> it
> simulates multi mice and update these mouse point by an function. And now,
> i
> try to pass my detected position and use this function to Achieve the
> goal.
So glad it's working for you, Mao. Remember to tell Raffaele also. Good
luck to you!
-- David
Nour El-Dien
Please tell me ASAP.
> On Friday, December 25, 2009 2:30 AM Mao wrote:
> Dear all:
> I am a junior engineer in SW. And now, i try to develop a software to
> simulate a touch screen's operation without any touch hardware. In win 7,
> these two message, wm_touch and wm_gesture, cannot be triggled directly by
> SendMessage and PostMessage. So In win7's touch architecture, these messages
> can only be triggled by a touch hardware? Or It can be triggled by other win
> api and other ways, like driver, to make it true?
>
>
> --
> ...
>> On Friday, December 25, 2009 7:02 PM David Ching wrote:
>> Why do you say they cannot be triggered with PostMessage()? Make sure the
>> app that is posting has the same privilege as the one handling WM_TOUCH (or
>> run the poster app As Administrator to be sure).
>>
>> -- David
>>> On Friday, December 25, 2009 10:00 PM Joseph M. Newcomer wrote:
>>> Have you tried? I was not aware that there was any possibility of restricting these so
>>> they could not be generated by SendMessage or PostMessage.
>>> joe
>>>
>>>
>>> Joseph M. Newcomer [MVP]
>>> email: newc...@flounder.com
>>> Web: http://www.flounder.com
>>> MVP Tips: http://www.flounder.com/mvp_tips.htm
>>>> On Saturday, December 26, 2009 12:05 AM Mao wrote:
>>>> "Note also that the touch input handle in this parameter is no longer valid
>>>> after the message has been forwarded using PostMessage, SendMessage, or one
>>>> of their variants. These functions will close and invalidate this handle."
>>>>
>>>> Above is the note in the MS MSDN's wm_touch description, and i had tried to
>>>> directly use postmessage and sendmessage in a button event, just like the
>>>> below example,
>>>>
>>>> MESSAGE_MAP
>>>> ON_MESSAGE(WM_TOUCH , OnTouch);
>>>>
>>>> void XXXX::OnBnClicked()
>>>> {
>>>> this->PostMessage(WM_TOUCH , wParam , lParam);
>>>> }
>>>>
>>>> the OnTouch function has also been added in my program, but when the
>>>> PostMessage transferred the WM_TOUCH message, my onTouch function doestn't be
>>>> triggled. Furthermore, if i changed the WM_TOUCH to any other Message, like
>>>> WM_LBUTTONDOWN, the program processing is also correct(onTouch can be
>>>> triggled). So i think whether the wm_touch message cannot be directly triggled
>>>> if i have no any touch hardware. Or by other ways to triggle these message.
>>>>
>>>> Thanks for reply....
>>>> --
>>>> ...
>>>>
>>>>
>>>> "Joseph M. Newcomer" wrote:
>>>>> On Saturday, December 26, 2009 12:20 AM Mao wrote:
>>>>> "Note also that the touch input handle in this parameter is no longer valid
>>>>> after the message has been forwarded using PostMessage, SendMessage, or one
>>>>> of their variants. These functions will close and invalidate this handle."
>>>>>
>>>>> Above is the note in the MS MSDN's wm_touch description. How to make sure
>>>>> the privilege as the one handling WM_TOUCH? If i have no privilege to handle
>>>>> WM_TOUCH, the privilege how to get?
>>>>> PS: In my program, if i change wm_touch to other messages, like
>>>>> WM_LBUTTONDOWN, the program process can work correctly, but wm_touch cannot.
>>>>> --
>>>>> ...
>>>>>> On Saturday, December 26, 2009 6:49 AM David Ching wrote:
>>>>>> This refers to the lParam of WM_TOUCH; it becomes invalid after you post the
>>>>>> message again, but it does not say you cannot PostMessage(WM_TOUCH). In fact,
>>>>>> by saying the above, Microsoft seems to be saying that you *can* call
>>>>>> PostMessage(WM_TOUCH), with the limitation mentioned (that lParam becomes
>>>>>> invalid).
>>>>>>
>>>>>>
>>>>>> Interesting. but if you post WM_LBUTTONDOWN, your app needs to changed to
>>>>>> add ON_WM_LBUTTONDOWN, as this is the appropriate message map entry for that
>>>>>> message. So maybe MFC message map is not set up correctly (although I do
>>>>>> see your code follows the example in
>>>>>> http://msdn.microsoft.com/en-us/library/dd371581%28VS.85%29.aspx).
>>>>>>
>>>>>> To eliminate message map, try overriding your class's WndProc() and see if
>>>>>> you get WM_TOUCH there. BTW, I do not have Win 7 SDK installed. What is
>>>>>> WM_TOUCH #define to?
>>>>>>
>>>>>> And can you try running your app in another OS besides Windows 7 (that does
>>>>>> not know anything about WM_TOUCH); see if you then receive WM_TOUCH message?
>>>>>> If so, then we know Win 7 somehow treats that message specially. (But I
>>>>>> do not think so, WM_TOUCH is just another predefined windows message).
>>>>>>
>>>>>> -- David
>>>>>>> On Saturday, December 26, 2009 6:52 AM David Ching wrote:
>>>>>>> I meant in general an app with a lower privilege cannot PostMessage to an app
>>>>>>> with a higher privilege. Windows will block the receiver app from ever
>>>>>>> seeing the message. But in your code you put in another posting you are
>>>>>>> posting to the same app, so this is not an issue.
>>>>>>>
>>>>>>> -- David
>>>>>>>> On Saturday, December 26, 2009 10:27 AM Mao wrote:
>>>>>>>> After your reminder, i can see what my problem is. In Win7, after triggering
>>>>>>>> wm_touch message, the lParam is a handle of the TOUCHINPUT and is used to get
>>>>>>>> the touch points' information. In fact, i have no touch hardware to create
>>>>>>>> this handle automatically. So, in the viewpoint of software, i can create any
>>>>>>>> a handle to make wm_touch message occurred? If so, the problem may be solved.
>>>>>>>> But if the handle's information is checked whether is a TOUCHINPT's handle or
>>>>>>>> not, it means that it must need a hardware?
>>>>>>>> Thx for your reply~~~
>>>>>>>>> On Saturday, December 26, 2009 12:25 PM David Ching wrote:
>>>>>>>>> I do not think Windows validates the handle before passing the message. I
>>>>>>>>> think instead is it keeps a static copy of the TOUCHINPUT data until the
>>>>>>>>> message is processed, at which time it thinks your app is done with it, so
>>>>>>>>> it frees the TOUCHINPUT data.
>>>>>>>>>
>>>>>>>>> Just pass NULL for lParam and capture the message in WndProc() like I
>>>>>>>>> suggested and see if you get it.
>>>>>>>>>
>>>>>>>>> -- David
>>>>>>>>>> On Sunday, December 27, 2009 4:39 AM Mao wrote:
>>>>>>>>>> Thanks for your suggestion. But unfortunately, I take lParam as NULL, and
>>>>>>>>>> pass to the event. It also cannot be triggered. So the handle, lParam, plays
>>>>>>>>>> an important role (For OS to judge whether a touch handle or not). I think
>>>>>>>>>> that the handle is created and connected to the touch's hardware is also
>>>>>>>>>> needed in the Win 7 touch's architecture, is not it? So, a touch handle
>>>>>>>>>> connect to a hardware can be simulated by an API?
>>>>>>>>>> --
>>>>>>>>>> ...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "David Ching" wrote:
>>>>>>>>>>> On Sunday, December 27, 2009 12:13 PM David Ching wrote:
>>>>>>>>>>> I am sorry but I do not know about the hardware requirements from WM_TOUCH and
>>>>>>>>>>> WM_GESTURE. I do know about using PostMessage to simulate messages received
>>>>>>>>>>> from the system and have never before encountered one that calling
>>>>>>>>>>> PostMessage() did not actually generate a message because Windows was "smart
>>>>>>>>>>> enough" to try to interpret the lParam and figure it was bogus.
>>>>>>>>>>> Unfortunately, I do not have time to install the Win 7 SDK and try it myself.
>>>>>>>>>>> Did you override CWnd::WindProc() as I suggested to see if you receive
>>>>>>>>>>> WM_TOUCH there? That's about all I can suggest, sorry.
>>>>>>>>>>>
>>>>>>>>>>> -- David
>>>>>>>>>>>> On Sunday, December 27, 2009 8:33 PM Mao wrote:
>>>>>>>>>>>> Never mind!!!! I will keep on trying it. Thank you very much.
>>>>>>>>>>>> --
>>>>>>>>>>>>> On Monday, December 28, 2009 8:14 PM David Ching wrote:
>>>>>>>>>>>>> I confirm your findings that posting WM_TOUCH (0x0240) to the same window
>>>>>>>>>>>>> results in the message not being received when run on Windows 7. When
>>>>>>>>>>>>> running the same app on Vista, the message is received. So Windows 7 is
>>>>>>>>>>>>> preventing the message from being posted. Calling RegisterTouchWindow() has
>>>>>>>>>>>>> no effect on this. Sorry I could not help more. The Touch API is still so
>>>>>>>>>>>>> new there are few people who know short of Microsoft.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- David
>>>>>>>>>>>>>> On Tuesday, December 29, 2009 12:12 PM David Ching wrote:
>>>>>>>>>>>>>> I have run your situation past a few C++ people at Microsoft. First responses
>>>>>>>>>>>>>> speculate ntuser is not forwarding the posted WM_TOUCH message due to
>>>>>>>>>>>>>> invalid parameters. It was news to me that ntuser validates message
>>>>>>>>>>>>>> parameters in PostMessage(), but there you go. Will let you know if
>>>>>>>>>>>>>> anything more definitive comes up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regardless, it was also pointed out that even if you successfully did post
>>>>>>>>>>>>>> WM_TOUCH, your app still would not be useful because you would not know what
>>>>>>>>>>>>>> info to post (the lParam HTOUCHINFO) because you would need to match what
>>>>>>>>>>>>>> the hardware sends, and you do not know what the hardware sends because you
>>>>>>>>>>>>>> do not have any hardware. So this whole approach of posting WM_TOUCH will
>>>>>>>>>>>>>> probably not get very far.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Another approach is to call SendInput() to generate the WM_TOUCH messages,
>>>>>>>>>>>>>> but alas this API (or at least the doc of it) has not been updated to support
>>>>>>>>>>>>>> Touch parameters.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The easiest way is probably to go buy a Touch enabled Windows 7 PC, sorry.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -- David
>>>>>>>>>>>>>>> On Friday, January 01, 2010 5:39 PM David Ching wrote:
>>>>>>>>>>>>>>> Another Microsoft MVP, Raffaele Rialdi, suggests:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If this helps you, please let him know (it is his blog in the first link).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> David
>>>>>>>>>>>>>>>> On Tuesday, January 05, 2010 2:18 AM Mao wrote:
>>>>>>>>>>>>>>>> Dear David:
>>>>>>>>>>>>>>>> Thanks for your help!!! I replace the way to post WM_TOUCH message with
>>>>>>>>>>>>>>>> using MultiTouchVista to simulate the Touch operation. In MultiTouchVista, it
>>>>>>>>>>>>>>>> simulates multi mice and update these mouse point by an function. And now, i
>>>>>>>>>>>>>>>> try to pass my detected position and use this function to Achieve the goal.
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "David Ching" wrote:
>>>>>>>>>>>>>>>>> On Tuesday, January 05, 2010 4:34 PM David Ching wrote:
>>>>>>>>>>>>>>>>> So glad it is working for you, Mao. Remember to tell Raffaele also. Good
>>>>>>>>>>>>>>>>> luck to you!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -- David
>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe
>>>>>>>>>>>>>>>>> ASP.NET Composite Controls
>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/e74c2318-9545-482a-90e2-65916778e72d/aspnet-composite-controls.aspx
Nour El-Dien
Please tell me ASAP.
>>>>>>>>>> --
>>>>>>>>>> ...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "David Ching" wrote:
>>>>>>>>>>>>>>> Another Microsoft MVP, Raffaele Rialdi, suggests:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If this helps you, please let him know (it is his blog in the first link).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> David
>>>>>>>>>>>>>>>> On Tuesday, January 05, 2010 2:18 AM Mao wrote:
>>>>>>>>>>>>>>>> Dear David:
>>>>>>>>>>>>>>>> Thanks for your help!!! I replace the way to post WM_TOUCH message with
>>>>>>>>>>>>>>>> using MultiTouchVista to simulate the Touch operation. In MultiTouchVista, it
>>>>>>>>>>>>>>>> simulates multi mice and update these mouse point by an function. And now, i
>>>>>>>>>>>>>>>> try to pass my detected position and use this function to Achieve the goal.
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "David Ching" wrote:
>>>>>>>>>>>>>>>>> On Tuesday, January 05, 2010 4:34 PM David Ching wrote:
>>>>>>>>>>>>>>>>> So glad it is working for you, Mao. Remember to tell Raffaele also. Good
>>>>>>>>>>>>>>>>> luck to you!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -- David
>>>>>>>>>>>>>>>>>> On Saturday, November 13, 2010 7:45 AM Nour El-Dien wrote:
>>>>>>>>>>>>>>>>>> Please, how can you send WM_Touch Message from MutliTouchVista project, where is this code exactly?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Please tell me ASAP.
>>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe
>>>>>>>>>>>>>>>>>> Silverlight 4 Coin-Flip Decision Maker based on Mersenne Twister
>>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/fabf1bbb-9568-4ff6-859b-7679bc02f13f/silverlight-4-coinflip-decision-maker-based-on-mersenne-twister.aspx
Nour El-Dien
Please tell me ASAP.
>>>>>>>>>> --
>>>>>>>>>> ...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "David Ching" wrote:
>>>>>>>>>>>>>>> Another Microsoft MVP, Raffaele Rialdi, suggests:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If this helps you, please let him know (it is his blog in the first link).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> David
>>>>>>>>>>>>>>>> On Tuesday, January 05, 2010 2:18 AM Mao wrote:
>>>>>>>>>>>>>>>> Dear David:
>>>>>>>>>>>>>>>> Thanks for your help!!! I replace the way to post WM_TOUCH message with
>>>>>>>>>>>>>>>> using MultiTouchVista to simulate the Touch operation. In MultiTouchVista, it
>>>>>>>>>>>>>>>> simulates multi mice and update these mouse point by an function. And now, i
>>>>>>>>>>>>>>>> try to pass my detected position and use this function to Achieve the goal.
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "David Ching" wrote:
>>>>>>>>>>>>>>>>> On Tuesday, January 05, 2010 4:34 PM David Ching wrote:
>>>>>>>>>>>>>>>>> So glad it is working for you, Mao. Remember to tell Raffaele also. Good
>>>>>>>>>>>>>>>>> luck to you!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -- David
>>>>>>>>>>>>>>>>>> On Saturday, November 13, 2010 7:45 AM Nour El-Dien wrote:
>>>>>>>>>>>>>>>>>> Please, how can you send WM_Touch Message from MutliTouchVista project, where is this code exactly?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Please tell me ASAP.
>>>>>>>>>>>>>>>>>>> On Saturday, November 13, 2010 7:47 AM Nour El-Dien wrote:
>>>>>>>>>>>>>>>>>>> Please, how can you send WM_Touch Message from MutliTouchVista project, where is this code exactly?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Please tell me ASAP.
>>>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe
>>>>>>>>>>>>>>>>>>> Merging SharePoint List Data into Word Documents
>>>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/6054abc5-c5fb-4e86-a352-afd0e8c4a7c6/merging-sharepoint-list-data-into-word-documents.aspx
Joseph M. Newcomer
asked, and you should only post the question once.
I nearly deleted this message because the subject made it look like spam. I don't have
the answer, but maybe someone who did thought it WAS spam and deleted it without reading
it.
joe
David Ching
> news:201011137...@eggheadcafe.com...
>
> Please, how can you send WM_Touch Message from MutliTouchVista project,
> where is this code exactly?
>
See Raffaele's article:
http://www.iamraf.net/Articles/SurfRaf-home-made-surface-for-Windows-7
The MultiTouchVista is linked there.
-- David