Subj : Using Prf* routines in wi
To   : IAN MOOTE
From : MIKE RUSKAI
Date : Tue Aug 01 2000 08:31 am

Some senseless babbling from Ian Moote to Mike Ruskai
on 07-28-00  20:49 about Using Prf* routines in wi...

 IM> Sorry for the lengthy delay. My host was down for a couple of weeks, 
 IM> then I got busy here in the shop and in my personal life.

 MR> Sort of.  The window procedure should do everything necessary to
 MR> maintain the window itself, short of long paints (which should be
 MR> done on a separate thread), and dispatch threads for the real work.
 MR> Ideally, that is.
 MR>
 MR> One way of making that easier is to set up a second message queue,
 MR> that doesn't have a window associated with it, which receives all
 MR> messages from the main window procedure via WinPostMsg() that aren't
 MR> to be done in that main procedure.

 IM> That would also require its own thread to process the messages on the 
 IM> second queue? Would I be correct in understanding that this is just a 
 IM> "technique" thing, something that you would do just to give the
 IM> program  more structure so that it behaves in a more logical fashion,
 IM> but which  does not really benefit the user of the program in a
 IM> noticeable or  practical way? (I'm not trying to sound critical here,
 IM> just trying to  understand where the suggestion is coming from.)

Yes, it would execute on its own thread.  And yes, it is a technique, the
point of which is to make the program noticeably better behaved.

Mike Ruskai
thannymeister@yahoo.com


.... Ah, Camelot. <It's only a model> Shhhh!

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/Wildcat5! v3.0pr3
 * Origin: Get all your fido mail here.. www.docsplace.org  (1:3603/140)

.