testurm@immd4.informatik.uni-erlangen.de (Torsten Sturm) (06/26/91)
Hi, i've got a problem about PeekMessage :
(I used PeekMessage in a normal while-look a lot, so I
thought I know all about it ???)
What I want to do is something like this :
for(......)
{
/* see, if other apps wish to do something and "eat" all mesg. for this
appl. */
PeekMessage(&msg,hWnd,0,0,PM_REMOVE);
.... do some calculating stuff (no SDK calls)....
}
The result is, that only messages, which are directly sent to other
window procedures come thru to other apps(I can see this with clock.exe
or cpuuse.exe from cica), such as WM_PAINT or WM_TIMER.
But I can't for instance click upon and activate another application.
I experienced with various parameter in PeekMessage, but nothing
changes !?!?!
What is wrong ??
Please help !
Thanx
---
Torsten Sturm
tnsturm@faui09.informatik.uni-erlangen.de
tnsturm@faui40.informatik.uni-erlangen.de
testurm@faui41.informatik.uni-erlangen.de
testurm@faui43.informatik.uni-erlangen.de
storm@faui80.informatik.uni-erlangen.debonneau@hyper.hyper.com (Paul Bonneau) (06/29/91)
In article <1991Jun26.120949.2873@informatik.uni-erlangen.de> testurm@immd4.informatik.uni-erlangen.de (Torsten Sturm) writes: >Hi, i've got a problem about PeekMessage : > >(I used PeekMessage in a normal while-look a lot, so I > thought I know all about it ???) > >What I want to do is something like this : > >for(......) >{ >/* see, if other apps wish to do something and "eat" all mesg. for this > appl. */ > PeekMessage(&msg,hWnd,0,0,PM_REMOVE); > >.... do some calculating stuff (no SDK calls).... >} > > >The result is, that only messages, which are directly sent to other >window procedures come thru to other apps(I can see this with clock.exe >or cpuuse.exe from cica), such as WM_PAINT or WM_TIMER. >But I can't for instance click upon and activate another application. > I would guess that by eating all messages for the apo in question, that you are disabling the process whereby windows activate another application. Perhaps the lack of response to the WM_NCHITTEST message is causing the problem. To get more of a feeling for the problem, try using spy on the other app you are clicking on and record the messages when the initial conditions are: (ie before you click on the other app) a) another "normal" app is active (notepad or something like that, and b) your app is active. Hope this helps. cheers - Paul Bonneau.