Re: wm_touch and wm_gesture Message

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sun, 27 Dec 2009 09:13:23 -0800

Message-ID:

<Og3dmfxhKHA.5568@TK2MSFTNGP02.phx.gbl>

"Mao" <Mao@discussions.microsoft.com> wrote in message
news:01FE152A-A1DA-454F-BA73-CB4C41BC6F6F@microsoft.com...

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