Yes. VS 2015 is the latest. See Win32-Desktop-Apps at Tools for Windows Apps and Games | Visual Studio[^]. See also Visual C++ in Visual Studio 2015[^] and MFC Desktop Applications[^].

I found it. I was creating the CMFCTooltipCtrl class improperly. Thanks for the effort, Barry

BarryPearlman wrote: If not and the button has to be subclassed, how do I do this. Subclassing Controls. Also check here. "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

Thanks everyone!

This wasn't meant as a philosophical discussion. If you enclose an important function call, e.g. the creation of a dialog in an ASSERT(), the dialog will not be created in Release mode and therefore can't receive any messages. If you use VERIFY(), the dialog will be created in Release mode as well. However, the "arcance message" as you call it, will only be displayed in Debug mode. The good thing about pessimism is, that you are always either right or pleasently surprised.

The documentation[^] explains what the function does, and suggests that it should be called immediately after a Window is created. This has always been my understanding, and the remainder of the time you just use InvalidateRect or InvalidateRgn to queue the redrawing messages. Veni, vidi, abiit domum

Try a "Rebuild" rather than a build to ensure that all old object files are cleaned up. If that still fails try a "Clean", followed by a manual delete of all "Debug" and "Release" directories in the Solution and Project directories. Once you have removed those try a "Build" again. If the problem still persists then post the actual error messages and people will try to help you. speaking as ...

The view would ow the buttons. The document is, effectively, your model, so it will contain any data that you need. *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington "Mind bleach! Send me mind bleach!" - Nagy Vilmos CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Please allow me to take this to the next level. The map is used to hold class pointers cast to (DWORD)*. When retrieved (CMap->Lookup(...)), they are cast back to theit original type and used. The number of elements at any given point in time in the map varies depending upon how many classes have been created or destroyed. When the application closes, the remaining map entries are cast back to their original pointers then deleted; the map is then destroyed. Obviously, if I just destroy the map, I am left with memory leaks of varying classes. The question occurs when I am down to just one map entry and it is time to close the application and destroy the last pointer cast DWORD*. How do I retrieve the last remaining item in the map?

BarryPearlman wrote: Worked like a charm; all leaks stopped to date. I haven't touched C++ & MFC in years and I forgot the basic rule of "when you are done with your crayons, put them away!" Thanks for your reply I'm glad to be of help. It would be great if you could mark the helpful answers (by clicking "Good Answer") and close your thread. “Follow your bliss.” – Joseph Campbell

:thumbsup: «_Superman_» I love work. It gives me something to do between weekends. Microsoft MVP (Visual C++)

BarryPearlman wrote: I do find it interesting that some people declare pointers as Class *pointer = and some as Class* pPointer. I use the second syntax, as that was the way I was taught. Actually, both work out to the same thing. I also use the second syntax. Recommended idiom in a C++ context is to use the second way. I also find it easier to read, especially when it comes to declaring reference arguments. However, it's not a big deal and I think it's not something that's pushed in style guides. Kevin