Newsgroups: comp.windows.ms.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!ames!haven.umd.edu!socrates.umd.edu!uc780.umd.edu!coates
From: coates@uc780.umd.edu
Subject: RE: Static Windows and MoveWindow
Message-ID: <9JUN91.16342798@uc780.umd.edu>
Sender: news@socrates.umd.edu (News)
Organization: The University of Maryland University College
References: <5194@servax0.essex.ac.uk> <675826491@f521.n281.z2.fidonet.org>
Date: Sun, 9 Jun 1991 16:34:27 GMT

In a previous article, jeroen_pluimers@f521.n281.z2.fidonet.org (Jeroen Pluimers) wrote:
>Hello Whiteside!
> 
>In a msg of <22 May 91>, Whiteside S D B writes to All:
> 
> WSDB> One a more general note: all this message passing seems highly
> WSDB> confusing. It seems to go back on the idea that functions should have
> WSDB> no side-effects. It's very hard to work out what's happening - what
> 
>Use a utility like SPY (from the windows SDK) to view all messages that reach 
>your window. That should help.
> 
> 
> 
>jeroen

Messages provide a way for Windows to have multitasking. Each program has
message queues in Windows for each of its windows. Unless you issue
UpdateWindow(), it's up to Windows on when a program's window will receive
a message
Also it is the backbone of the object orientation for Windows, in that
a programs windows are sent messages and th window does its thing based
on the algorithms and data it has a result of its particualr window process
or function.

***********************************************************************
*                   Elliott Coates, Washington DC                     *
*                                                                     *
*                       coates@uc780.umd.edu                          *
***********************************************************************