And the gdiplus.dll plonked alongside all the other wx dlls in the
distributed “wx” folder.
I’ve found a few references to this problem and all seem to be linux
based issues when configuring the build. Is there something I need to
turn on in the wxPython build to get GDI included?
And the gdiplus.dll plonked alongside all the other wx dlls in the
distributed “wx” folder.
I’ve found a few references to this problem and all seem to be linux
based issues when configuring the build. Is there something I need to
turn on in the wxPython build to get GDI included?
The demo UltimateListCtrl works when it's run against a binary distrib
of wxPython installed into the site-packages of my main Python 2.6. It
doesn't work when I use the wxWdigets/wxPython build I've described
below running in a virtual env which doesn't share that site-packages.
So there's something missing or simply wrong with the builds we're
doing.
Again, thanks for any insight someone might have,
Luke
···
On Jul 19, 7:29 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
On Jul 19, 10:55 am, Luke Tunmer <luke.tun...@gmail.com> wrote:
> Hi,
> I’m getting this error on from a Windows hybrid build of wxPython when
> running the UltimateListCtrl demo.
> We build this version using the following command line to build
> wxWidgets:
> And the gdiplus.dll plonked alongside all the other wx dlls in the
> distributed “wx” folder.
> I’ve found a few references to this problem and all seem to be linux
> based issues when configuring the build. Is there something I need to
> turn on in the wxPython build to get GDI included?
> Many thanks for any help,
> Luke
Which version of wxPython? Does the widget work in the wxPython demo?
Thanks, Robin. That file was indeed not being updated with the changed
setup.h, so I've modified our make rules.
However, it still doesn't work.
It seems that the _gdi_wrap.cpp is the culprit in that it short
circuits the constructors for the wxGCDC class to raise this Python
error. I assume this means I need to re-SWIG (the file is like this as
part of the source distrib), which up to now I had not needed to worry
about?
Many thanks
Luke
···
On Jul 20, 4:39 am, Robin Dunn <ro...@alldunn.com> wrote:
On 7/19/10 8:55 AM, Luke Tunmer wrote:
> I have the flag below set in the setup.h file:
> #define wxUSE_GRAPHICS_CONTEXT 1
The setup.h gets copied to another location as part of the build, so
make sure that the one in $(WXWIN)/lib/vc_dll/mswuh has that #define too.
--
Robin Dunn
Software Craftsmanhttp://wxPython.org
Never mind. It seems that "clean" is not really clean enough. By
trashing the entire source tree and rebuilding it, it then built with
gdi on. I'm cooking on gas now!
Thanks for your help.
Regards,
Luke
···
On Jul 20, 12:53 pm, Luke Tunmer <luke.tun...@gmail.com> wrote:
Thanks, Robin. That file was indeed not being updated with the changed
setup.h, so I've modified our make rules.
However, it still doesn't work.
It seems that the _gdi_wrap.cpp is the culprit in that it short
circuits the constructors for the wxGCDC class to raise this Python
error. I assume this means I need to re-SWIG (the file is like this as
part of the source distrib), which up to now I had not needed to worry
about?
Many thanks
Luke
On Jul 20, 4:39 am, Robin Dunn <ro...@alldunn.com> wrote:
> On 7/19/10 8:55 AM, Luke Tunmer wrote:
> > I have the flag below set in the setup.h file:
> > #define wxUSE_GRAPHICS_CONTEXT 1
> The setup.h gets copied to another location as part of the build, so
> make sure that the one in $(WXWIN)/lib/vc_dll/mswuh has that #define too.
> --
> Robin Dunn
> Software Craftsmanhttp://wxPython.org