🚀 go-pugleaf

risto@tuura.UUCP (Risto Lankinen) writes:
>lwallace@javelin.es.com (Raptor) writes:
>>I've sent WM_KEYUPs and WM_KEYDOWNs to other applications, and used Spy to
>>examine them.

>Since you cannot be sure whether the target reacts upon WM_KEYUP/DOWN or
>the resulting WM_CHAR/SYSCHAR/MENUCHAR message, you should not send these
>messages with SendMessage(), because they bypass the target application's
>TranslateMessage() call in its message loop.  You should use PostMessage()
>instead, which allows the target app. to translate the WM_KEYUP/DOWN's as
>appropriate.

Hey, thanks for answering!  I'm getting desperate about this problem;
it's one of two that are keeping me from getting my application done.

Alas, I misinformed you.  I do indeed use PostMessage(), with the same
lack of results.

Lately, I've tried both SetFocus() (before sending the messages) and
WaitMessage() (between the KEYDOWN and KEYUP messages) to see if I was
hogging any resources and preventing the other application from
processing my messages.  No improvement.

Why in the heck does SDKHelp work and all these others don't??????  A
possible hint is, the keystroke I'm sending SDKHelp is F1, while all
the other attempts have been control-characters (requiring two
messages...).  I've used Spy again and tried to get my messages to
appear *exactly* as the actual keystrokes, but there's only so much
I've been able to accomplish to that end.

Again, thanks for the input.
-- 
Lynn Wallace			   |I am not an official representative of
Evans and Sutherland Computer Corp.| <- E&S.  Or for that matter, unofficial.
Salt Lake City, UT 84108	   |Internet: lwallace@javelin.sim.es.com
			War not make one great! -- Yoda