Hi,
first sorry for my bad english.
i cant find a solution about my problem in this forum:
why have i memory leaks when including the ogre.h in a standard mfc application (for example a dialog-based mfc application).
including the ogre.h in a "normal" win32-based application cause no problems.
i using Visual Studio.Net 2003.
thanks for your patience
Newton1976
Memory leaks when include ogre.h in mfc?
-
Newton1976
- Gnoblar
- Posts: 3
- Joined: Tue Feb 01, 2005 9:31 pm
- Location: Germany - Saarland
- sinbad
- OGRE Retired Team Member

- Posts: 19269
- Joined: Sun Oct 06, 2002 11:19 pm
- Location: Guernsey, Channel Islands
- x 67
- Contact:
Try surrounding your MFC includes with:
I never use MFC but I believe it's one of those things that doesn't like to co-exist with the memory manager.
Code: Select all
#include "OgreNoMemoryMacros.h"
.. MFC
#include "OgreMemoryMacros.h"
-
Newton1976
- Gnoblar
- Posts: 3
- Joined: Tue Feb 01, 2005 9:31 pm
- Location: Germany - Saarland
- sinbad
- OGRE Retired Team Member

- Posts: 19269
- Joined: Sun Oct 06, 2002 11:19 pm
- Location: Guernsey, Channel Islands
- x 67
- Contact:
-
Newton1976
- Gnoblar
- Posts: 3
- Joined: Tue Feb 01, 2005 9:31 pm
- Location: Germany - Saarland
- johnhpus
- Platinum Sponsor

- Posts: 1186
- Joined: Sat Apr 17, 2004 2:49 am
- x 3
Just to avoid confusion ... if it hasn't changed the mesh viewer uses WTL instead of MFC.
If your familiar with MFC you can also check out the wxWidgets tutorial that comes with Ogre and work from there. It shows you what you need to do, but it's up to you to figure out where to do that in an MFC app.
Good luck,
John
If your familiar with MFC you can also check out the wxWidgets tutorial that comes with Ogre and work from there. It shows you what you need to do, but it's up to you to figure out where to do that in an MFC app.
Good luck,
John