🚀 go-pugleaf

Robert G. Hoover wrote:
> So in general, 1 thread (my main app) processes event messages and 1 
> thread (my
> own creation) grabs a video frame from the camera into a BITMAP buffer and
> paints it on the screen using SetDIBits or StretchDIBits.

You can't do this though, because those functions aren't thread safe :-) You 
have to use either DirectShow, Direct3D or DrawDib. Or if you wish to have 
the work done for you, you can look at VideoLab by Mitov Software, in 
particular the TVLImageDisplay or TVLDSImageDisplay. http://www.mitov.com


> My problem is hard to diagnose. My symptoms are general slowness of video
> refresh/update, reduced frame rate, OS crashes (blue DOS screen as "auto
> restart" is disabled) with messages like IRQL_LESS_OR_EQUAL or 
> BAD_POOL_HEADER.
>
> A complicating factor to this is that the GUI updates in response to user
> interaction. This is for a robotics app. So, when motors move, their 
> absolute
> positions are displayed immediately thru TLabel::Repaint().

Are you updating the labels from another thread?

> I've surrounded calls to the GUI with try/catch blocks. Is it possible 
> this is related to my
> problem?

Possibly - but I need more info regarding how you update the GUI.


> Perhaps if I configure my entire program to use a single side of the
> processor then it will behave like it does on single-core machines? Can I 
> do that?

Possibly, but if you fix this problem, your app will be much better, plus 
probably faster :-)

HTH

Jon