C / C++ / MFC

memory leaks with IMPLEMENT_DYNACREATE

6-Oct-04 9:22

A simple dirty way is this:
declare a global varibale:

<br />
bool bIgnoreMouse = false;

in the message handler for your mouse disabling button:

<br />
bIgnoreMouse = true;<code><br />
<br />
in your mousehandlers:<code><br />
if( bIgnoreMouse )<br />
return;<br />
// else execute your code

Hope this helps

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

jhorstkamp6-Oct-04 7:57

jhorstkamp

6-Oct-04 7:57

All,

My VC7 debugger is catching memory leaks (I inherited a project with a lot of "new" and not a lot of "delete"...) which I am in the process of cleaning up. Several of the "caught" leaks take me to the IMPLEMENT_DYNACREATE macro in a few classes, most notably the MainFrm.cpp, the view class.cpp and the doc class.cpp files when I click on them in the debug window. I don't know where to go from there. Any suggestions?

Thanks in advance,

John

Re: memory leaks with IMPLEMENT_DYNACREATE

Iain Clarke, Warrior Programmer6-Oct-04 12:11

Iain Clarke, Warrior Programmer

6-Oct-04 12:11

You need to look for things like...

RUNTIME_CLASS (CLeakingObject)
and
CRuntimeClass->CreateObject ();

and so on.

If you look at the definition of the macro,
you can see the Create functions it hides.

Iain.

Re: memory leaks with IMPLEMENT_DYNACREATE

jhorstkamp7-Oct-04 8:49

jhorstkamp

7-Oct-04 8:49

Thanks - not sure I understand...

Clicking on one of the memory leak messages in the debug window takes me to:
IMPLEMENT_DYNCREATE(CPalsView, CScrollView)

The next is:
IMPLEMENT_DYNCREATE(CMainFrame, CFrameWnd)

and the last is:
IMPLEMENT_DYNCREATE(CPalsDoc, CDocument)

does this mean that it thinks I (or maybe MFC) has a memory leak in one of these classes?
The only place I see the RUNTIME_CLASS macro is here in the App.InitInstance function:

CSingleDocTemplate* pDocTemplate;
pDocTemplate = new CSingleDocTemplate(
IDR_MAINFRAME,
RUNTIME_CLASS(CPalsDoc),
RUNTIME_CLASS(CMainFrame), // main SDI frame window
RUNTIME_CLASS(CPalsView));
AddDocTemplate(pDocTemplate);

which is of course a memory leak since I can't seem to find a cooresponding delete (unless MFC is handling that in some hidden way) ????

Any comments?

Statusbar gettext functionality

4apai6-Oct-04 7:40

4apai

6-Oct-04 7:40

Need your advertisment on the following subject.
Does anybody know how to obtain the text from the statusbar?
Simple call of the GetWindowText retrieve only the text in first cell if is.
How to get the text from the others areas, is a question for me...

Any ideas?

4apai
There're no impossible tasks. There're tasks that required infinite period of execution time.

Re: Statusbar gettext functionality

Iain Clarke, Warrior Programmer6-Oct-04 12:07

Iain Clarke, Warrior Programmer

6-Oct-04 12:07

Have look at CStatusBar::GetPaneText (...).

Iain.

Esc key how i can stop his job

medlteam6-Oct-04 7:39

medlteam

6-Oct-04 7:39

when i design any program use MFC Dialog box if u press Esc key ur program will end and if i want save setting when my program end but if i press Esc offcourse y program didnot save any thing so how i can stop Esc effect in my program or how i make any effect if i press it like save setting or else..
plz any one help me

Re: Esc key how i can stop his job

David Crow6-Oct-04 8:02

Re: Esc key how i can stop his job

6-Oct-04 8:02

Override the dialog's OnCancel() method. See here for more.

"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

anandforu6-Oct-04 9:02

anandforu

6-Oct-04 9:02

you should use an Keyboard hook.(key board filter function)
use SetWindowsHookEx,
lowlevelkeyborad event.

#pragma warning(disable:...) does not work?

Bob Stanneveld6-Oct-04 6:33

6-Oct-04 6:33

Hello,

I'm trying to disable some compiler warnings generated while using the stl. The warnings that I try to disable are:
4663, 4018, 4100, 4786, 4245, 4146, 4244.

I installed the latest service pack and processor pack for visual studio 6.

Does anybody have a clue why these warnings do not get disabled?

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

David Crow6-Oct-04 7:29

6-Oct-04 7:29

Where are you placing the #pragma directives?

"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

Bob Stanneveld6-Oct-04 7:32

6-Oct-04 7:32

At the top of my precompiled header file "StdAfx.h".

But I found some article here on codeproject that explains that some stl headers are setting the warnings back to default (on). Because of that my #pragma is everruled by the stl...

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

David Crow6-Oct-04 7:58

6-Oct-04 7:58

I understand the article's intent, but it seems excessive. I placed the following in my project's stdafx.h file right before any other STL includes:

#include <yvals.h>
#pragma warning(disable:4018 4100 4146 4244 4663)
 
// other STL includes begin here
#include <iostream>

"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

Bob Stanneveld6-Oct-04 9:18

6-Oct-04 9:18

And you get a clean build? If I do that, the warnings keep on coming...

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

David Crow6-Oct-04 9:24

6-Oct-04 9:24

Bob Stanneveld wrote:
And you get a clean build?

Yes, for those particular warnings.

"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

Bob Stanneveld6-Oct-04 9:26

6-Oct-04 9:26

Do you also have the latest sdk installed?

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

David Crow6-Oct-04 9:31

6-Oct-04 9:31

I have the Febuary 2003 (5.2.3790.0) edition installed.

"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

Bob Stanneveld6-Oct-04 9:53

6-Oct-04 9:53

And now I'm starting to think that some paranormal influence wants me to go crazy... Confused | :confused:

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

David Crow6-Oct-04 10:04

6-Oct-04 10:04

Please show the contents of your project's stdafx.h file.

"When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

Bob Stanneveld6-Oct-04 10:11

6-Oct-04 10:11

#ifndef __StdAfx_h_included__
#define __StdAfx_h_included__

#define VC_EXTRALEAN

#include <afx.h>
#include <afxwin.h>

/*
// these didn't work
#pragma warning(disable: 4018)
#pragma warning(disable: 4100)
#pragma warning(disable: 4146)
#pragma warning(disable: 4244)
#pragma warning(disable: 4245)
#pragma warning(disable: 4511)
#pragma warning(disable: 4512)
#pragma warning(disable: 4663)
#pragma warning(disable: 4710)
#pragma warning(disable: 4786)
*/

// warning 4018 still falls through
#define STL_USING_STRING
#include "Stl.h"

#endif // __StdAfx_h_included__

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

Solved!

Bob Stanneveld6-Oct-04 10:19

6-Oct-04 10:19

I finally solved it. Big Grin | :-D

After digging through the slt headers for a long time, I discovered that in the header <xlocale> the warnings 4018 and 4663 get set to their default state.
The solution was editing the Stl.h file in the STRING section so that those warnings get disabled after <xlocale> was included...

Now I can go to sleep with a clear mind...

Thanks for your help Big Grin | :-D

Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.