Click here to Skip to main content
15,891,607 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
VS2013 debug window refresh code, VS2013 always loses the response, how to do?


C#
case WM_PAINT:
   hdc = BeginPaint(hWnd, &ps);
   // TODO: add your code...

  DrawTest(hWnd, hdc);   //<-debug location,add a breakpoint,loss of response to VS2013

  EndPaint(hWnd, &ps);
   break;
  case WM_DESTROY:
Posted
Comments
Sergey Alexandrovich Kryukov 7-Nov-14 19:43pm    
Huh? What does it mean, exactly? People handle and debug WM_PAINT thousands of times...
—SA

1 solution

Debugging WM_PAINT is problematic because it interacts with the GUI. My tip is to add some TRACE output and only a single draw statement after one other to see where the problem is.

In your case we need to see whats in the DrawTest. Maybe the VS2013 isnt so perfect :-O
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900