Yes, i believe it. This bug used to catch me all the time. Now i've learned to always do ON_MESSAGE handlers the LRESULT way. there is a "ON_MESSAGE_VOID" message handler, but i've never used it and i don't know if it will help. (from Afxpriv.h) // like ON_MESSAGE but no return value #define ON_MESSAGE_VOID(message, memberFxn) \ { message, 0, 0, 0, AfxSig_vv, \ (AFX_PMSG)(AFX_PMSGW)(void (AFX_MSG_CALL CWnd::*)(void))&memberFxn }, -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com

You must use CPaintDC in OnPaint because CPaintDC calls BeginPaint() and EndPaint() to validate the window regions when a WM_PAINT message is sent. Look up CPaintDC and read the documentation. When you select a pen or brush into the DC but do not unselect it (by selecting the original resource), then when the CPen or CBrush goes out of scope, the destructor attempts to delete the brush or pen, but cannot because it's selected in the DC. That means the delete fails and the resource is never deleted. You don't have to explicitly delete the brushes or pens, since this is done automatically by the destructor of the CPen or CBrush object, so long as the brush or pen is not currently selected in a DC.

I got the same problem too. I try to resolve it by disable the scroll bar in CListBox,and insert a CScrollBar to control all CListBoxes. But, very weird is that I can not see any usable message for scrollbar in ClassWizard!? Does anybody know why? How could I control a Scroll bar? I really need help!:(

> Is there any workaround or setting that the modal dialog appears aligned to my parent > even if I move my parent out of the visible part of the screen.    How about obtaining the geometry of your parent window when processing WM_INITDIALOG, and use SetWindowPos() or similar on the modal dialog to the coreect location?    Peace! -=- James.

> The question is what will happen with a mutex-object which owner is no longer running ?    The documentation says that the handle to a created/obtained Mutex object is automatically closed when the process terminates.  I am not sure if that includes abnormal termination.  I am *fairly* certain I have had Mutex objects get "orphaned" on me in the past.    But the thing I would concerned about is not really abnormal termination of your process, but your process trying to shut down, but cannot, because of a rogue/blocked thread, or something like that.  You app will *appear* to have shut down to the user, but will still be sitting in the background someplace.  Of course, you should try to prevent stuff like this from happening, but Sh*t Happens! :eek:    MSDEV tends to do that to me at least twice a day (goes to sleep in the background after a shutdown)! :)    Peace! -=- James.