If you include Windows.h befre including SmartWin++ you
get lots of weird bugs due to double definitions...
If this is possible to fix we should do so...
Logged In: NO
In addition to Windows.h, I hope you support this common
Some of my projects use afx.h, afxwin.h, and afxdisp.h
instead of windows.h. Doing this DOES NOT cause my
project to link to MFC, but it does cause the inclusion of OLE
(which I sometimes require).
When including these headers, windows.h cannot be used in
This is what I have in my stdafx.h for projects that require OLE
but not MFC. Note that most includes are commented out but
shown here for completeness:
#define VC_EXTRALEAN // Exclude rarely-used
stuff from Windows headers
#include <afxwin.h> // MFC core and standard
//#include <afxext.h> // MFC extensions
//#include <afxdtctl.h> // MFC support for Internet
Explorer 4 Common Controls
//#include <afxcmn.h> // MFC support for
Windows Common Controls
//#endif // _AFX_NO_AFXCMN_SUPPORT
Logged In: YES
I am not realy sure if inclusion of afx.h etc will work, but
this is something we should look into yes!
I tried this but it appears t work, at least in the
Regarding the afx.h it gives me linking errors so this is a
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.