Pecan,
Excellent, I am able to build the class wizard AND have it running without crashing.
Many thanks for your solution !!!
I am glad to know that I did not screw up with import lib's and dll's, I was very sure I was doing that part correctly.
Since during the build of plug-in dll, the only references to wx are the header files, the problem should be in one of those.
The patch contains new versions of :
.cpp (should be of no importance to our issue) :
window.cpp
tbar95.cpp
splitter.cpp
notebook.cp
helpchm.cpp
grid.cpp
.h (the problem was probably in here)
listbox.h (2 changes, from which 1 code change)
notebook.h (seems to be unchanged)
uxthemep.h (1 change / different include)
window.h (2 changes, from which 1 code change)
The generated setup.h is identical.
Just an idea :
Maybe we could have some people testing the sdk part of the delivery, a test suite could be : compile all build-in plug-ins by using the sdk. We do need for every plug-in then a cbp project file, preferably as minimal as possible.
So compiler switches and include paths which are not needed should be out of the cbp. This way thinks become more clearer, and one get's more focus on the thing that do matter.
You can count me in for such a testing group.
And indeed the wiki needs to be updated to contain this kind of information. Do note, that the wiki entry is going all te hawy, even building cb, and then maybe the problems won't happen, since then everything is really using the same sources, dunno ??
Change for window.h : added
// some controls (e.g. wxListBox) need to set the return value themselves
//
// return true to let parent handle it if we don't, false otherwise
virtual bool MSWShouldPropagatePrintChild()
{
return true;
}
Change for uxtheme.h :
#include <commctrl.h>
becomes
#include "wx/msw/wrapcctl.h"
Change for listbox.h : added
// under XP when using "transition effect for menus and tooltips" if we
// return true for WM_PRINTCLIENT here then it causes noticable slowdown
virtual bool MSWShouldPropagatePrintChild()
{
return false;
}
What do the core developers think of this, ensuring to get an ever better usable sdk ?
kind regards,
Lieven