I'm doing my first non-VCL program and am having real trouble with with "not
responding" (as shown in Task Manager).
Everything is fine until I click away from my application and on to another.
After that my program's WinProc procedure doesn't seem to get sent any
messages, even when the mouse is moved over and/or clicked inside my window.
Here's where is gets complicated. My app is using DirectDraw to create a
full-screen application on my secondary monitor. It creates only one window
which is used for both the device and the focus window (That part seems to
work fine). This window and my "WinProc" procedure are created/run on a
secondary thread.
My primary (and others) thread is definately running because I can see it
doing animation.
So I'm wondering if an applications WinProc procedure *has* to be on its
primary thread? I hope not because this will screw up my design.
Any help greatly appreciated as I'm at the end of my tether with this.
--
Jay
Jason Burgon - author of Graphic Vision
http://homepage.ntlworld.com/gvision
