liuty2006 wrote: I want to display a text file into a view derived from CScrollView Any reason why you do not want to use CEditView? Nish "I'm a bit bored at the moment so I'm thinking about writing a new programming language" - Colin Davies My book :- Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

Both macros are adding the ability to query runtime information with CObject::IsKindOf for the classes. But only classes declared with DECLARE_DYNCREATE are enabled to be created by CRuntimeClass::CreateObject. Normally all views used inside the "MFC-Document-View-Architecture" were created by the framework by a call to CRuntimeClass::CreateObject. Hope this helps. Best regards Holger Persch

hi are you trying to destroy a window in that window's class deconstructor? I think when deconstructor is called, the window is already destroyed, so no message can be sent to it,like WM_DESTROY( which invokes OnDestroy).

liuty2006 wrote: what I would pay special attention to, when i write programe? Any data that is written by more than one thread should be wrapped in a critical section, or similar, to ensure atomic access. Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002

I cover this at length in my article on functors. Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002 Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002 Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002

Since you've already got that intel, I think you may have seen Detecting and Isolating Memory Leaks Using Microsoft Visual C++[^]. Further in that article, there's a section called Comparing Memory States. If you suspect code that's leaking, wrap it with a call to checkpoint the memory before, and after, then compare. The article gives an example. "The greatest danger to humanity is humanity without an open mind."   - Ian Mariano - http://www.ian-space.com/