Prev: linking with mfc42.lib and mfc90.lib?
Next: decoding character encoding confusion
From: David Wilkinson on 12 May 2008 07:32
Simon wrote:
> When I'm debugging GDI calls it would be very helpful if every time my code
> called a GDI function (e.g. Polyline) I could see immediately what effect it
> has on the screen. Normally what happens is that you step over that line of
> code and see nothing on the screen. In fact normally it isn't until I have
> executed the entire paint function that I see the results. But by then it's
> too late to determine which line of code did what.
>
> I can understand why this is. But for debugging purposes, it would be very
> handy if I could get the screen to update after each GDI call. Does anyone
> know of any way of doing this? I use VC++ 6.

Simon:

Just sprinkle UpdateWindow()'s in the code?

--
David Wilkinson
Visual C++ MVP
 | 
Pages: 1
Prev: linking with mfc42.lib and mfc90.lib?
Next: decoding character encoding confusion