How to catch (and hopefully fix) a GDI resource leak?

Recently I've created a simple class that calls GetGuiResources() function in both the constructor and destructor and reports any differences in GDI object counts. Using it as a scoped object in a few functions helped me plug GDI leaks in the code.

GDIView worked for me. It pointed to a Font leak. I did a search for ToHfont().

The rest is history.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.