CCriticalSection problem. Pls help!

[a_du]

I have a dialog which contains a CListCtrl to dislplay some information. two cwinthreads from other dlg keep updating the data of the CListCtrl. the CListCtrl's handle is passed to the threads and there is a Shared CriticalSection among these 3 objects. when i close the dlg, i want to set a flg to inform the two threads that the list is destroyed. so i call in the exit event of the dlg: lock.Lock(); destroyFlg = true; // the threads will check this flg before access the list //and access to the list is protected by lock & unlock lock.UnLock(); what happend is that , the dlg is hung. i traced and find it hung at lock.Lock(); there is only one crictical section and i am sure i have paired each lock() with a unlock(). why this still happend? Some one knows please help me. thanx a lot. :(

[David Crow]

a_du wrote: two cwinthreads from other dlg keep updating the data of the CListCtrl. You can avoid a whole lot of problems by simply having these other two threads post a message back to the main thread (the one that actually owns the GUI). Locking and synchronizing are a headache if not done 100% correctly.

---

"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

[Anonymous]

Consider using a wrapper class to lock your object. See following code: http://code.axter.com/sync\_ptr.h The above wrapper class will automatically lock and unlock your object, so you don't have to worry about forgetting.