Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!tandem!netcom!wolf
From: wolf@netcom.COM (Buckskin Tech.)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Detecting full-screen DOS session
Message-ID: <1991Apr18.214912.9598@netcom.COM>
Date: 18 Apr 91 21:49:12 GMT
References: <11748@jarthur.Claremont.EDU>
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 20

jseidman@jarthur.Claremont.EDU (Jim Seidman) writes:

>Bonus question:  Can anyone guess why a program in a PeekMessage() loop
>(which is yielding control) would go through the loop several times more
>often when a (non-exclusive) DOS session was full-screen than when the
>same DOS session was windowed and in the foreground?  (And no, the
>PeekMessage loop isn't doing graphics or anything like that...)

>Jim Seidman, Headland Technology, 46221 Landing Parkway, Fremont CA 94538
>UUCP: ames!vsi1!headland!jls                 INTERNET: hsv3!jls@apple.com
>"Love your enemy, smite your enemy, you still need an enemy!"
>					-Joseph, in "Heart of the World"

I'd suspect that since the DOS session is full-screen, a) the timeslicer
is running and it's anybody's guess as to timing issues, and b) Windows
may "know" that no human input will reach your app (no focus, no mouse, etc)
so it's not spending any time correlating mousemoves and such.  The "holes"
in the queue might then show up to PeekMessage().

 - Wolf