Here is an annoying problem that I’m sure other people have faced and overcome before.
I’m finding that my
paint() method is overloaded with redundant calls, probably due to my trigger-happy use of
repaint() and other poor design choices. I’d like to examine the call stack to see what’s going on, but if I set a break-point in
paint() it is immediately triggered and gets stuck in a loop when I press “continue”. I don’t quite understand it, but it’s something to do with the app window going in and out of focus as the “continue” button is pressed, which in turn calls
Is there any way of using conditional break-points or something so that the program will ignore
paint() calls from changes to the window focus? If not, is there some other way that I can examine the call stack for the
I’m using Visual Studio Community.